We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 8d ago. Scan again before you trade.
- WARNHoneypot
- WARNChecks with missing data
- WARNHolder concentration
No current verdict. The last complete check is from 2026-10-22 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 8d ago. Scan again before you trade.
Price
$0.000047
Liquidity
$9,253
Volume 24h
$5,908
FDV
$45,416
Buys 24h
33
27 sells
Age
34d 5h
Our sell test passed on the routes we measured, but that does not show whether the hook can stop a sale.
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.)
Top 10 holders hold 35.7% of the circulating float.
On raw total supply that's 27.2%, because 23.8% 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 5.9% of the float on its own.
Deepest pool holds $9,253.
These are gaps in what we could see, not problems found in this token.
45 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, 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.
Only 0.0% of this pool's liquidity could be traced to a holder, so no conclusion is drawn about who controls it.
This pool is on Uniswap V4 and holds 99.7% 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.
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.
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 5× liquidity, a proportionate ratio.
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 a hook that can change what a trade pays out, and we have not established a limit on it.
24h turnover 0.6× liquidity.
Trading profile is proportionate (0.6× 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.
Bytecode did not match any known clone template.
Pool is 622h old.
Contract deployed 622h ago.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.