Trade with care. Read the warnings first.
Top 10 holders hold 62% of the tokens in circulation.
Scanned 1d ago. Scan again before you trade.
- FAILHolder concentration
- WARNHoneypot
- WARNPrior pump-and-dump mark
DexProof recorded GOONER as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1583 published 29 Oct 2026 (UTC). Of 28 checks, 13 passed, 4 warned, 1 failed and 10 could not be run.
Trade with care. Read the warnings first.
Top 10 holders hold 62% of the tokens in circulation.
Scanned 1d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Top 10 holders hold 62% of the tokens in circulation.
The largest holder is , a plain wallet, holding 12.7% of the tokens in circulation on its own. Against total supply, the top 10 hold 11.2%. Liquidity pools hold 81.9% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades.
We couldn't finish the sell test on the other exchanges we checked.
At least one pool did not pass its sell test and could not be shown too small to matter, so we can't say this token can be sold everywhere.
This token crashed after launch.
On 2026-09-20, its price or liquidity fell 95% or more below its 72-hour peak, and a second data source confirmed it. This often happens when early buyers sell. On its own it does not mean the contract or its liquidity is unsafe.
We couldn't read some checks on this scan, so the verdict is limited.
A failed read is not a clean result. This describes what we could see, not the token.
The deployer (), a contract, holds 100.0% of the liquidity backing this V4 pool at the current price.
This contract is not a trusted locker, so this liquidity is not considered locked. Its controller or contract code may still move or withdraw it. The contract needs an audit before we can say more. This pool is on Uniswap V4 and holds 100.0% of the liquidity we could read. One other pool charges a fee too large to trade through, so nothing a holder owns is at risk there.
These are gaps in what we could see, not problems found in this token.
Applies to: Funder rug history, Deployer launch history, Funding lineage, Tax manipulation
So we can't check for past rugs, because many people launch through it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check its past launches. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't trace who funded it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check whether it changed fees or limits.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
We could not find when this token's pool was created.
A contract deployed this token, but that contract is not in the launchpad registry.
So we can't tell where it launched. 5.0% of the token supply was bought by 1 wallet in the transaction that opened its pool, before outside buyers could trade.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
No liquidity removal by the wallet that launched this token from its own pool.
The creator's recent history has no removal calls either.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
The contract has no owner function, so it has no single owner wallet.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is partially verified on the explorer, matched from another address with identical bytecode, not proven against this one.
We found no mint, pause, blacklist or limit functions in the token contract's code.
It also has 17 functions we couldn't identify (0x02d05d3f, 0x10f5c407, 0x1f7979a2, 0x24024efd, and 13 more). You may want to look at them. The contract's own published source names every one of them.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This token's code doesn't match any code template we know of.
This contract was 60 days old at this scan.
The source is partially verified through a bytecode match, so the code can be read.
We could not match it to a known template.