A clearer view of the signals that shape a market.
Bring wallet movement, pool conditions, and unusual activity into one deliberate workspace. The current dashboard is an interactive product preview—not a live data terminal.
The Sinkers dashboard is designed to help people inspect on-chain activity without confusing a polished interface for verified market intelligence. Its layout brings together the context a researcher may need: selected assets, notable wallet events, pool changes, and alert severity. In this preview, every displayed value is illustrative. No RPC connection, indexer, market feed, or user account is attached.
A focused view of on-chain activity.
Sample event rhythm
Illustrative pattern only; no market feed is connected.
Activity clusters
Example alert stream
Sample labels and timestamps are illustrative. Watchlist changes are temporary and are not saved.
One workspace, separate evidence streams
A monitoring screen is most useful when it separates what happened from what it might mean. A transfer is an on-chain fact once confirmed; calling it a sale, a coordinated exit, or a price signal requires additional context. Sinkers is designed around that distinction, presenting event type, asset, time, and verification state before interpretation.
The overview can be organized around watched assets and recent activity rather than unsupported global totals. This keeps the first screen readable and makes it easier to move from a signal to its underlying transaction, pool, or contract details. In a production release, each panel would identify its source and last successful update.
Focus the view around assets you follow
Watchlists are intended to make repeated research faster. A user could group tokens by a thesis, ecosystem, or research project, then apply filters for event type, time window, pool, or severity. The present preview lets you filter sample rows locally; it does not save a list to an account or monitor a token in the background.
A future persisted watchlist should make ownership explicit, validate token addresses against BNB Smart Chain, and let users remove items without needing a wallet signature. Browsing public information should never require a wallet connection.
Severity is a prioritization aid, not a verdict
An alert classification can help triage a busy feed, but it is not a prediction. A low, medium, or high label should be supported by a documented rule—such as a threshold relative to recent pool depth—and should show the evidence behind that rule. Alerts need to distinguish confirmed events from provisional observations.
The sample alert cards in this preview are marked DEMO DATA. They are not sourced from current blocks and should not be used to make a trading decision. When verified data is available, the interface should show the chain, block, transaction hash, and a link to an independent explorer.
Follow large transfers back to their context
A large transfer can represent many things: a custody movement, a treasury operation, a bridge action, a market-making adjustment, or a trade. A dashboard should make wallet labels and classification confidence visible, and provide a path to verify the transaction independently.
The Whale Watch view is built to connect with this area. It will explain how transfer size is normalized, why labels can be incomplete, and which wallet relationships are known versus inferred. Until an indexing pipeline is available, no wallet movement is presented here as live.
Pair activity with pool and contract information
The amount of liquidity in a pool can affect the price impact of a hypothetical order, but reserve snapshots can change quickly and may not capture every route or fee. A useful panel would state which pool and block its reserves came from and avoid presenting an estimate as an executable quote.
Risk Scanner is a separate research aid for reviewing public contract properties. Its output should show the exact source fields and caveats rather than reduce a complicated contract to a single safety score. Explore the Liquidity Radar and Risk Scanner pages for the intended interpretation.
From a signal to a reproducible review
A responsible workflow starts with a notification, checks the transaction and pool state, and then considers broader context. The dashboard is planned to link an alert directly to a wallet activity timeline, liquidity history, and relevant contract information so that users can reproduce a conclusion rather than accept a label.
Data freshness, source coverage, and known blind spots should remain visible throughout that workflow. For the current product direction, review Technology for the planned data path and Documentation for the product guides.
Good questions deserve clear answers.
These notes reflect the current prototype status. For product details, follow the linked guides and their stated limits.
Is this dashboard connected to live BNB Chain data?
No. It is a front-end preview with clearly marked DEMO DATA. No RPC provider or event indexer is configured.
Can I save a watchlist?
The preview filter is temporary and browser-side. Account-backed watchlists are not implemented yet.
Are alert levels predictions?
No. An alert can flag a rule-based observation; it cannot guarantee a price move or outcome.
THE INTELLIGENCE BEHIND EVERY MARKET SIGNAL.
Stay ahead by staying curious. Verify the event, question the interpretation, and keep the limits in view.