How holder data works

A wallet counts as a known whale if it currently ranks among the top real-wallet holders of any one of the platform's 30 largest tokens by market cap, or of STONK itself (the platform's own token, tracked separately and much more deeply — see below): a live, on-chain fact, not a self-reported or platform-assigned label. A fresh launch whose early holders already rank among the top holders of the platform's biggest tokens is a very different animal from one held entirely by unfamiliar addresses, and unlike a creator wallet, a top-ranked position like that can't be faked by spinning up a new address.

Which tokens are tracked, and how deep

The registry is built from a live on-chain holder scan of the 30 tokens with the highest market cap at the time it's built (re-checked every 30 minutes, so the tracked list itself can change as market caps move), each scanned to a depth of 20 holders. STONK is tracked separately and by name, not by its incidental market-cap ranking — it's scanned 250 holders deep instead of 20, since it's the platform's own token and a much larger pool of its holders is worth tracking as smart money. If STONK also happens to rank in the top 30 by market cap (likely, given its size), it isn't scanned twice — the deeper 250-holder scan is the only one used for it. A token is never counted as a whale of itself: the tag only ever refers to a wallet's standing in some other leading token.

What a token's own “known whales” count means

On a token's Holders panel, “Known whales” is how many of that token's own top holders also qualify as a known whale of a leading platform token or of STONK, and the percentage next to it (“hold 9.3%”) is how much of this token's supply those wallets hold together: a read on how much of what you're looking at is held by wallets with an established, verifiable track record elsewhere on the platform.

Whale status is decided from each tracked token's top real-wallet holders by rank: 20 deep for the platform's other 30 largest tokens — the same depth the Holders panel itself resolves and classifies for every token — and 250 deep for STONK specifically. Because the underlying holder scan reads every token account on chain and sorts by balance before slicing to that depth, the cutoff is always the true top N by rank, never an artifact of scan order or partial coverage.

Program-owned accounts (liquidity pools, bonding-curve vaults, escrows) are excluded outright. A pool holding size isn't a signal about a person; only real wallets can be known whales.

Beyond the crown badges on a token's own holder table, a wallet's known-whale standing follows it: expand any holder row (or open a wallet's full portfolio) to see every platform token it's a known whale of, not just the one you started on.

marks the badge wherever it appears: on a holder row, a wallet's portfolio page, or your own connected wallet.

Whales activity tab

The token sidebar's Whales tab and the full Whales page show the same feed. By default it shows the core cohort: the top 10 holders of the platform's 10 largest tokens. Each minute the scanner rechecks another 25 of those wallets, so the whole cohort comes round every few minutes. Wide net adds every registry wallet holding at least 0.5% of a tracked token's supply.

A wallet outside the core cohort that made a verified trade in the last 6 hours is rechecked on a faster round of its own, another 40 of them a minute, so an active wallet's next trade shows up well before the full rotation would reach it. How long that round takes depends on how many wallets are active; the tab's Coverage section gives the current figure.

Wallets outside the core cohort are checked on a slower rotation through the rest of the registry, another 8 per minute, reading up to 25 transactions newer than each wallet's last check. The tab's Coverage section shows how recently the core cohort was checked and this pass's attempted, failed, and unreadable counts; a full pass takes time, and that progress is part of the meaning of an empty feed. A transaction whose lookup fails is tried again, within the scan and then on the wallet's next scans for up to 10 minutes; “unreadable” counts only the ones still unread after that, which is the only way a verified trade can go missing from the feed.

Each trade shows its size as a share of supply and the wallet's position before and after, read from the transaction's own token accounts (other token accounts the wallet owns aren't included). Market cap is shown only when the trade was detected within minutes of happening.

On the Whales page, a card's Top 1 / Top 10 / Top 20 row is how much of the traded coin its largest wallets hold, with pools and other program-owned accounts left out. Each figure needs a full holder scan, so the scanner fills them in one coin a minute, starting with the most recently traded, and a coin whose top holders couldn't all be classified shows no row rather than a guess.

The feed keeps the newest 3,000 verified trades across batches and deploys, at most 150 per wallet (so one wallet trading every minute can't push everyone else's history out) and none older than 7 days. Tracked wallets trade often enough that the count is reached long before the age limit; the tab's Coverage section says how far back the history reaches right now. The newest 300 load first, “Load older trades” fetches the next page, and “This coin” on a token page searches the whole history for that coin.

Simple SOL, USDC, and StonkFun-approved custom-pair swaps are supported by matching the two wallet balance changes to the project's declared paired asset. Complex multi-asset routes stay excluded rather than being guessed into a buy or sell.