HOODLOCK / LEARN

Reading holder distribution on Robinhood Chain.

Published 2026-07-27 · HoodLock Team

The holder list answers a question no chart can: if a handful of wallets decided to sell tomorrow, would there be anything left. On Robinhood Chain it's two minutes of reading on Blockscout, and most people never open it.

Where to look

Every block explorer has a holders tab on the token page. It ranks addresses by balance and shows each one's share of total supply. On Robinhood Chain that's the Blockscout token page for the contract address.

Exclude these before you panic

The top entries are usually supposed to hold a lot. Reading the raw list without filtering them out will make almost every token look dangerous:

Most explorers mark contract addresses with an icon. What's left after removing them is the number that matters: how much supply sits in wallets that can sell at any moment.

Reading the number

Top 10 wallets (contracts excluded)What it means
Under 15%Genuinely distributed. Rare outside established tokens.
15–30%Normal for a young project. Watch the largest single holder.
30–50%Concentrated. A few holders set the price.
Over 50%The market is those wallets. Everyone else is a passenger.

One wallet at 20% is more dangerous than ten wallets at 3% each, because coordination isn't required. Look at the shape of the distribution, not just the total.

Three ways the list gets manipulated

  1. Splitting across wallets. One holder becomes twenty addresses of 1% each, funded from the same source. Check whether the top wallets were funded by the same address and around the same time — the explorer shows first-transaction history.
  2. Pre-launch supply burns. Burning half the supply before launch halves everyone's percentage on paper. A wallet that held 20% of the original supply now displays as 10% of a smaller total while holding exactly the same tokens.
  3. Parking supply in a contract that isn't a lock. A large balance in a contract looks reassuring, but only a real locker or vesting contract restricts withdrawal. Open the contract and check what it actually does.

What a healthy distribution looks like

For a project that's set things up properly, the biggest holders should be explainable: the liquidity pool, a locker holding LP, a vesting contract holding the team allocation, and a treasury address. When a team's allocation sits in a vesting schedule rather than a wallet, it shows up in the holder list as a contract with a proof page you can read — the distribution and the commitment become the same fact.

Put it together

Holder distribution answers "who can dump on me." It doesn't answer whether liquidity can be pulled. That's a separate check, or whether you can sell at all, which is the honeypot question. Run all three.

Common questions

What is a healthy token holder distribution?

After excluding contracts such as the liquidity pool, lockers, vesting contracts and burn addresses, top-ten wallet concentration under about 30% is normal for a young project. Above 50% in wallets means a handful of holders effectively set the price.

Which addresses should I exclude from the holder list?

Exclude the liquidity pool contract, locker and vesting contracts, burn addresses, and bridge or staking contracts. These hold large balances by design. What matters is how much supply sits in ordinary wallets that can sell at any moment.

Can holder distribution be faked?

It can be made to look better than it is. A single holder can split across many wallets funded from the same source, and burning supply before launch shrinks everyone's percentage on paper without changing who holds what. Check funding history and first-transaction timing on the top wallets.

Is one large holder always a red flag?

Not if it's explainable. A large balance in a locker, vesting contract or the liquidity pool is expected. A large balance in an ordinary wallet with no lock behind it is the case worth worrying about.

Keep reading

See what's actually locked

Search a token and read its locks, burns and vesting straight from Robinhood Chain.

Check a token →