ROBINHOOD CHAIN · ID 4663
THE VERDICT
The last receipt on record for this token — not a live scan.
1 VERDICT ON RECORD
Top 10 holders hold 51.7% of the circulating float. On raw total supply that's 41.8%, because 19.1% of total supply sits in liquidity pools and is excluded from the float. The float figure is measured against supply outside the pools, so it also moves when pool liquidity moves. The single largest holder is , a contract, holding 40.0% of the float on behalf of holders this scan could not enumerate — that share is not proven to be under one key. Some of this supply is held inside a staking or escrow contract whose depositors could only be partly identified, so this share is reported at its highest supported reading.
Unverified contract source.
64 points of this token's scoring surface could not be read this scan, so the score is capped at 84 (the top of CAUTION). A check that stands down for want of data deducts nothing, so without this cap a failed read would look the same as a clean result. This is about what we could see, not about the token.
Pool is 0.1h old, under the 48h line.
Fingerprint UNKNOWN and source unverified: the bytecode is opaque.
DTF scores 76 — CAUTION. Holder concentration is the one that moved it, 10 points off. Ask me why.
DRAWN FROM THIS VERDICT’S CHECKS — NOT A MODEL ANSWER
OPENS THE PANEL — THAT IS WHERE YOU TYPE
Sell quotes through the (hookless) pool: exitable. A direct transfer probe also clears the token's own transfer layer, which the V4 Quoter alone cannot exercise.
Explorer answered but recorded no creator for this contract, and this token's pools gave no conclusive custody answer either.
No owner() function, and the contract's source is unverified, so its authority surface could not be enumerated and ownerlessness is not established.
Not an upgradeable proxy. The code is fixed.
Unverified contract source.
No mint/pause/blacklist/limit functions found in bytecode.
Explorer unreachable. Source data unavailable.
Heads up: the scanner is improved continuously, and some fixes only surface once they meet real tokens on production. Our trusted registry — verified LP lockers, known-good launchpad contracts — is checked and approved by a human on the team, so a legitimate project can score lower for a while until we've confirmed its contracts ourselves. A low score is a prompt to look closer, not a conclusion.
Ask why this verdict reads the way it does.