We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 13d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- FAILHolder concentration
- WARNChecks with missing data
No current verdict. The last complete check is from 2026-10-17 under an older formula (v1.60). Scan the token again for a current verdict.
We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 13d 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 V3.
Top 10 holders hold 78.4% of the circulating float.
On raw total supply that's 17.8%, because 77.3% 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 smart-account wallet, holding 64.6% of the float on its own.
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.)
Contract bytecode matches 0xee04…e1f7, a token whose market later collapsed.
That describes the market, not who caused it. Any 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.
100.0% of the liquidity this scan could read is in a Uniswap V3 pool where its liquidity is locked.
Separately: Not counted: one of 8 V4 fee-tier pools for this token, outside the top 6 by active liquidity. The pools backing the price were assessed instead. (Shortened from the original receipt.)
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. The opening token deposit into pool contained no ETH. Its opening ETH came from buyers.
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.
Buy and sell both simulate cleanly, including as two independent fresh wallets paying this chain's live gas price (40172000 wei).
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.
The token contract has no privileged capabilities found in the audited source and bytecode.
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 1870h ago.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.