We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 12d ago. Scan again before you trade.
- FAILLP custody
- WARNHoneypot
- WARNChecks with missing data
No current verdict. The last complete check is from 2026-10-18 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 12d ago. Scan again before you trade.
Price
$0.0000146
Liquidity
$6,692
Volume 24h
$89.72
FDV
$14,175
Buys 24h
0
2 sells
Age
103d 8h
None of this V4 pool's liquidity is burned or locked.
The largest liquidity provider is , a plain wallet, and not the deployer. It controls 100.0% of this pool's liquidity and can withdraw it at any moment. Renouncing ownership does not protect against this. This pool is on Uniswap V4 and holds 26.4% of the liquidity this scan could read. One other pool charges a fee too large to trade through, so nothing a holder owns is at risk there. The deepest pool this scan could read (Uniswap V4, 55.5% of the liquidity we read) was assessed separately: its custody could not be fully traced.
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.)
Top 10 holders hold 47.9% of the circulating float.
On raw total supply that's 33.6%, because 29.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 8.6% of the float on its own.
Deepest pool holds $6,692.
Privileged capabilities present (amm route change) but every controlling authority is renounced or unreachable.
These are gaps in what we could see, not problems found in this token.
Only the creator's most recent transactions were read.
855 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.
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.
Launched on Sentry Launch Factory V4.
We do not track that launchpad's raises yet, so how much of the raise the creator bought was not measured.
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.
Ownership renounced (owner is the zero/dead address).
Not an upgradeable proxy.
The code is fixed.
Contract source is verified on the explorer.
FDV is 2× liquidity, a proportionate ratio.
24h turnover 0.0× liquidity.
Trading profile is proportionate (0.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.
Bytecode did not match any known clone template.
Pool is 2185h old.
Contract deployed 2185h ago.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.