The platform's smart-money layer: who the large holders are, what they hold, and what moved — with every figure's basis printed.
| Entity | Tracked value |
|---|---|
| Binance | $142.5B |
| OKX | $27.6B |
| Bitfinex | $22.6B |
| Robinhood | $14.1B |
| US Government | $12.8B |
| Bybit | $12.5B |
| Tether | $10.5B |
| Coinbase | $8.3B |
| Bitget | $7.0B |
| Mt. Gox | $6.2B |
'Smart money' in on-chain analysis means identified large holders — exchanges, funds, custodians, mining pools, whale clusters — whose behavior can be separated from the crowd because their wallets are known. DeepGyre's version of the discipline is deliberately conservative: an entity is an AGGREGATE of addresses the platform has verified belong to one controller (a labeled exchange's custody set, a fund's known wallets, a mined cluster), and every figure it prints carries its own basis — which addresses, verified how, measured when.
The tracker answers three questions. WHO holds: the entity leaderboard with tracked values. WHAT moved: flows between entity clusters and exchanges, the moments identified whales deposited to or withdrew from venues. WHEN it changed: the history a cluster's holdings, so a redistribution is visible as a change and not as noise.
The full tracker — live flow lists, per-entity drill-downs and alerts — is a dashboard module. This page embeds the public layer: the largest tracked entities by value, measured live from the platform's own aggregation.
Read entity rows as aggregates, not individuals: a cluster is many addresses under one verified controller, and its value is the sum across those addresses at the latest measured prices.
Exchange deposits and withdrawals carry different meaning — deposits precede potential sale; withdrawals from custody precede holding. The tracker separates them, because reading one as the other is how a custody shuffle becomes a rumor.
Check the basis line on every figure: which addresses, verified how, measured when. A row whose basis the platform cannot state is not shown at all — that rule is the difference between a measurement and a claim.
Entity data comes from the platform's own aggregation: address clusters verified into entities by the label engine and valued at the latest measured prices. A page view never triggers a provider fetch — the snapshot is the stored aggregation, and an entity that was never aggregated prints as 'no data yet' rather than zero.
Identified large holders: verified entity clusters — exchanges, funds, custodians, whale aggregates — whose wallets the platform has verified belong to one controller.
Through the label engine: known custody addresses, published wallet lists and clustering verified into one aggregate, with the basis printed on every figure the entity page shows.
The public layer — the entity leaderboard on this page and the entity pages — is free. The live flow tracker is a dashboard module; its plan gating is stated on /pricing.
You can track the entity a wallet belongs to, and watchlist addresses inside the dashboard. The platform tracks aggregates, not individuals — a single address is a wallet page, not an entity.
Because clustering and valuation choices differ between platforms. DeepGyre prints its own basis with every figure so a difference can be traced to its source instead of argued about.