We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 7d ago. Scan again before you trade.
- FAILLP custody
- WARNChecks with missing data
- WARNHolder concentration
No current verdict. The last complete check is from 2026-10-23 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 7d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
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 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.
On that scan, 8 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 45.8% of the circulating float.
On raw total supply that's 10.6%, because 76.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.9% of the float on its own.
Active owner key: .
Privileged capabilities present (limit change, a switch that can block transfers or selling, privileged code with assembly this audit could not read) but every controlling authority is renounced or unreachable.
Present but no longer exercisable: supply mint (initialize can only run once and already has), amm route change (initialize can only run once and already has), initialization (initialize can only run once and already has).
The same contract template has been deployed 15 times, a copycat pattern.
These are gaps in what we could see, not problems found in this token.
25 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, Funding lineage
That is a shared source such as an exchange, so its record is nobody's in particular.
That is a shared source such as an exchange, so whatever sits in its history belongs to that source rather than to this deployer.
We could not read this token's market data on this scan, so its pool depth was not measured.
This says what we could see, not what the token is.
Market data unavailable for FDV/liquidity ratio.
Market data unavailable for turnover.
Market data unavailable for wash-trade analysis.
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.
No canonical asset collision.
No scam tag on the explorer.
The token's main pool and every other pool large enough to matter let it be sold in our test.
5 hook-free pools are too small to matter and were set aside. This does not show how large a sale those pools can absorb, or that the Universal Router itself will execute it. A fresh wallet can also send this token to the pool, the transfer a sell actually makes, which the V4 Quoter alone cannot exercise.
This token is not on our list of confirmed rugs.
No prior honeypot on record.
No pump-and-dump on record.
This deployer has no earlier launches on record.
Not an upgradeable proxy.
The code is fixed.
Contract source is partially verified on the explorer.
The code matches, the compiler metadata does not. Read at its implementation .
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.
Contract deployed 1251h ago.
Fingerprint UNKNOWN, but the source is partially verified (bytecode-database match), so the code is readable.
Launched on Doppler, but its bonding curve stalled without graduating, so no DEX pool ever existed and there is nothing further for this check to say.