No current verdict. The last complete check is from 2026-10-23 under an older formula (v1.61). Scan the token again for a current verdict.
We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 7d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Sell execution could not be established on the other venues checked: At least one pool did not pass its sell test and could not be shown too small to matter, so the token-wide result is unresolved.
Sells on this pool go through a swap hook we could not verify. Our code check found no owner-set sell controls, but that does not show what the hook does to a sale.
On that scan, 8 checks had missing or incomplete data.
We couldn't work out who controls this token's liquidity. (Shortened from the original receipt.)
Top 10 holders hold 45.2% of the circulating float.
On raw total supply that's 7.8%, because 74.7% 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. A further 8.2% of total supply is held in a permanent launchpad locker with no withdrawal path, so it can never re-enter circulation and is excluded from the float. The single largest holder is , a contract, holding 10.0% of the float on its own.
These are gaps in what we could see, not problems found in this token.
Only the creator's most recent transactions were read.
557 transactions by the creator that could remove liquidity were not checked. A pull by the creator cannot be ruled out.
Applies to: Funder rug history, Funding lineage
That is a shared source such as an exchange, so its record is nobody's in particular.
That is a shared source such as an exchange, so whatever sits in its history belongs to that source rather than to this deployer.
Could not read this pool's liquidity events, so custody was not attributed.
This pool is on Uniswap V4 and holds 100.0% of the liquidity this scan could read. 3 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
We could not read this token's market data on this scan, so its pool depth was not measured.
This says what we could see, not what the token is.
Market data unavailable for FDV/liquidity ratio.
Market data unavailable for turnover.
Market data unavailable for wash-trade analysis.
This token was created by a contract, which sends no transactions of its own, so fee or limit changes by its creator could not be checked.
Pool creation time unavailable.
No canonical asset collision.
No scam tag on the explorer.
This token is not on our list of confirmed rugs.
No prior honeypot on record.
No pump-and-dump on record.
This deployer has no earlier launches on record.
No owner() function.
No single owner key surface.
Not an upgradeable proxy.
The code is fixed.
Contract source is verified on the explorer, but matched from another address with identical bytecode (a shared bytecode database) rather than proven against this one.
The token contract has no privileged capabilities found in the audited source and bytecode.
This is about the token contract only. Its main pool runs the Pons V2 Meme Hook, which can take up to 10% of each trade.
No active paid boosts on DexScreener.
The paid-order list could not be read this scan, so purchased listings are not covered by this result.
Bytecode did not match any known clone template.
Contract deployed 886h ago.
Launched on Pons V2 and graduated to a DEX pool.
Creator bought an unknown share of the raise. The pool's creation transaction could not be fully read this scan, so its launch buys are unknown.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.
Robinhood