We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 7d ago. Scan again before you trade.
- FAILHolder concentration
- WARNHoneypot
- WARNChecks with missing data
No current verdict. The last complete check is from 2026-10-23 under an older formula (v1.61). A new check is underway.
We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 7d ago. Scan again before you trade.
Price
$0.0000092
Liquidity
$11,068
Volume 24h
$587.69
FDV
$9,142
Buys 24h
0
11 sells
Age
98d 1h
Top 10 holders hold 71.1% of the circulating float.
On raw total supply that's 10.5%, because 85.2% 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 20.3% of the float on its own.
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, 5 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 $11,068, but only $3,289 of that is WETH, the side a seller receives.
The rest is this token's own supply. The opening token deposit into pool contained no ETH. Its opening ETH came from buyers.
These are gaps in what we could see, not problems found in this token.
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.
Could not read this pool's liquidity events, so custody was not attributed.
This pool is on Uniswap V3 and holds 100.0% of the liquidity this scan could read. 2 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
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.
No liquidity removal by this token's creator or the wallet that launched it from its own pool.
Other wallets removed liquidity from it 3 times, so this does not mean the pool is intact. None in the creator's recent history either.
This token is not on our list of confirmed rugs.
No prior honeypot on record.
No pump-and-dump 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.
FDV is 1× liquidity, a proportionate ratio.
The token contract has no privileged capabilities found in the audited source and bytecode.
24h turnover 0.1× liquidity.
Trading profile is proportionate (0.1× 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 2171h old.
Contract deployed 2171h ago.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.