We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 16d ago. Scan again before you trade.
- FAILHolder concentration
- WARNHoneypot
- WARNChecks with missing data
No current verdict. The last complete check is from 2026-10-14 under an older formula (v1.58). A new check is underway.
We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 16d ago. Scan again before you trade.
Price
$0.0005
Liquidity
$16,824
Volume 24h
$501.20
FDV
$51,675
Buys 24h
4
0 sells
Age
—
Top 10 holders hold 95.6% of the circulating float.
On raw total supply that's 70.8%, because 26.0% 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 , an address, holding 49.5% of the float on behalf of holders this scan could not enumerate, so that share is not proven to be under one key. Some of this supply is held inside a staking or escrow contract whose depositors could only be partly identified, so this share is reported at its highest supported reading.
Sell execution could not be established on the other venues checked: Sell simulation coverage is incomplete; 48 candidate route(s) were not attempted, so a token-wide conclusion is unsupported.
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, 7 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 $16,824, but only $3,774 of that is USDG, the side a seller receives.
The rest is this token's own supply.
These are gaps in what we could see, not problems found in this token.
219 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.
Could not read this pool's liquidity events, so custody was not attributed.
This pool is on Uniswap CL and holds 99.8% 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.
No owner() function; the audit resolved this contract's source as verified but still could not enumerate its 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.
Pool creation time unavailable.
This token was deployed by a contract, but that deployer is not in the launchpad registry, so its provenance could not be attributed.
17.8% of the token supply was bought by 5 wallets in the transaction that opened its pool, before outside buyers could trade.
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 verified on the explorer, but matched from another address with identical bytecode (a shared bytecode database) rather than proven against this one.
FDV is 3× liquidity, a proportionate ratio.
The token contract has no mint, pause, blacklist or limit functions in its bytecode.
It also has 3 functions whose names match a standard OpenZeppelin contract. Some of them can hand out permissions or move tokens on someone's behalf, for example burnFrom. We matched the names, not what the code behind them does.
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.
Contract deployed 1441h ago.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.