How holder data works

Every number on a token's Holders panel is read live from chain, not from StonkFun's own snapshot. This page covers the scan behind it and exactly what counts as a “known whale.”

§1

Known whales

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.

A rank, not an amount

The bar is “top N holders” of a tracked token, not a fixed token count: a wallet qualifies by rank, regardless of how large or small its actual balance is next to other tokens' whales. An earlier version of this page used a fixed minimum-token- count threshold instead; it's rank-based now so the registry reflects who actually holds meaningful, top-tier positions in each specific token, rather than one absolute bar that meant very different things on a token with a huge supply versus a tiny one.

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.

§2

Scan depth & coverage

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.

§3

Where this shows up

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 sidebar rotates through the entire current whale registry rather than repeatedly checking the same largest wallets. Each minute it attempts another 10 wallets and checks their latest 12 transactions. The tab shows this pass's attempted, successful, failed, and unreadable counts, plus the latest completed full pass. A full pass therefore takes time and the progress shown is part of the meaning of an empty feed.

Verified trades are retained for 7 days across batches and deploys. 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.