We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 21d ago. Scan again before you trade.
- FAILHolder concentration
- WARNHoneypot
- WARNChecks with missing data
No current verdict. The last complete check is from 2026-10-09 under an older formula (v1.56). A new check is underway.
We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 21d ago. Scan again before you trade.
Price
$0.0000064
Liquidity
$6,121
Volume 24h
$18,353
FDV
$6,230
Buys 24h
25
15 sells
Age
109d 11h
Top 10 holders hold 93.8% of the circulating float.
On raw total supply that's 17.9%, because 80.9% 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 plain wallet, holding 23.2% of the float on its own.
The V3 pool's sell test passed, but another route's test was not conclusive.
Sell simulation coverage is incomplete; 3 candidate route(s) were not attempted, so a token-wide conclusion is unsupported. Not every trading venue could be searched. The V3 result covers that pool only, so it does not show the token can be sold on every route.
On that scan, 6 checks had missing or incomplete data.
We couldn't work out who controls this token's liquidity. (Shortened from the original receipt.)
Deepest pool is valued at $6,121, but only $1,122 of that is WETH, the side a seller receives.
The rest is this token's own supply.
Privileged capabilities present but none can still be used.
Present but no longer exercisable: a switch that can block transfers or selling (setPool can only run once and already has).
These are gaps in what we could see, not problems found in this token.
Pool discovery for this token did not complete, so the set of pools searched for removals may be short and a deployer pull cannot be ruled out.
Applies to: Funder rug history, Deployer launch history, Funding lineage
Many people launch through the same contract, so rugs among the tokens it made are not one launcher's record. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so no history is attributed to that address.
Many people launch through the same contract, so its launch history is nobody's in particular. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so no history is attributed to that address.
Money paid into a contract like that is nobody's funding history in particular. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so no history is attributed to that address.
Pool discovery was incomplete: the uniswap-v4 leg did not answer whole, so the pool set may be missing a pool and no pool's share of it can be trusted.
No owner() function, but the contract audit could not attribute the contract's authority surface, so ownerlessness is not established.
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.
This token was deployed by a contract, but that deployer is not in the launchpad registry, so its provenance could not be attributed.
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.
Not an upgradeable proxy.
The code is fixed.
Contract source is partially verified on the explorer, matched from another address with identical bytecode rather than proven against this one.
FDV is 1× liquidity, a proportionate ratio.
24h turnover 3.0× liquidity.
Trading profile is proportionate (3.0× turnover).
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.
No risky serial-clone relationship found.
Pool is 2120h old.
Contract deployed 2120h ago.
Fingerprint UNKNOWN, but the source is partially verified (bytecode-database match), so the code is readable.