We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 7d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- FAILDangerous functions
- WARNHoneypot
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
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
The wallet that sent this token's launch transaction () removed liquidity from this token's own pool: 1 withdrawal on Uniswap V4.
It closed the position completely.
Privileged capabilities present and reachable via a live or unresolved authority: supply mint, initialization, address block, privileged code with assembly this audit could not read, upgrade code.
Sell execution could not be established on the other venues checked: No simulated route could be definitively classified; the token-wide result is unresolved.
On that scan, 10 checks had missing or incomplete data.
We couldn't work out who controls this token's liquidity. (Shortened from the original receipt.)
Active owner key: .
Upgradeable proxy with no EIP-1967 admin address.
This does not prove renunciation: UUPS or beacon upgrade authority may still be live.
Contract bytecode matches prior creator liquidity removal on 0x2003…09b6; creator link to this token is unverified.
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.
Pool has no active liquidity at the current price, so there is no custody share to measure.
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.
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.
Top 10 holders hold 3.3% of the circulating float.
On raw total supply that's 0.7%, because 77.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.
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.
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 783h ago.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.