Beets (BEETS)

As of the 2026-10-09 snapshot, BEETS scores 75/100 (grade B) on NexFlow's on-chain read — based on a contract that can mint new supply, cannot freeze or blacklist transfers, liquidity of $439.28K and 7,746 holders, with the creator wallet holding <0.01% of supply. That grades contract and market structure, not price direction — a clean read is not a guarantee, so re-scan before trading, since on-chain state can change.

The 2026-10-09 contract read found no sell-blocking controls on BEETS — no honeypot flag, no transfer pause, no blacklist — and every honeypot GoPlus positively flags is dropped from this index outright. That clears the contract side; how cleanly an exit fills still depends on your size against the $439.28K of measured depth.

The wallet that created BEETS holds <0.01% of the supply as of 2026-10-09 — a small stake, under the 5% the scanners flag. That sits alongside a holder base of 7,746; a broad base lowers the odds that any one seller can steer the price, but the creator's share is the number to watch first.

Yes — the contract can still mint new supply as of the 2026-10-09 snapshot, so the deployer or a minter role can dilute holders. Treat the circulating figure as a floor, not a cap.

The BEETS contract address on sonic is 0x2d0e0814e62d80056181f5cd932274405966e4f0. Always verify a token by its contract address, not its name or ticker — scam clones copy tickers, but the address is unique.

Run the live on-chain scan at the top of this page first; if BEETS clears, you can swap it here directly. Whatever venue you use, match the contract address (0x2d0e0814e62d80056181f5cd932274405966e4f0) exactly before trading — copying the ticker is how clone scams catch buyers, and the address is the one field they can't fake.