We couldn't finish this scan. Scan again before you trade.
No current verdict.
Scanned 8d ago. Scan again before you trade.
- WARNHoneypot
- WARNChecks with missing data
- WARNLP custody
No current verdict. The last complete check is from 2026-10-22 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 8d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Sell execution could not be established on the other venues checked: Sell simulation coverage is incomplete; 12 candidate route(s) were not attempted, so a token-wide sell-block conclusion is unsupported.
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.)
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 59.6% of the liquidity this scan could read. This pool was opened by . That wallet is not the token's creator and not its launchpad. The liquidity described above is that wallet's own position, not something the creator controls. Anyone can open a pool for any token.
Top 10 holders hold 45.8% of the circulating float.
On raw total supply that's 15.0%, because 59.1% 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. A further 8.2% of total supply is held in a permanent launchpad locker with no withdrawal path, so it can never re-enter circulation and is excluded from the float. The single largest holder is , a plain wallet, holding 10.2% of the float on its own.
These are gaps in what we could see, not problems found in this token.
No active rug markers were found in the funding records checked, but untraced wallet connections remain unknown.
The funds were sent through a batch-send contract.
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.
No liquidity removal by this token's creator or the wallet that launched it from its own pool.
None in the creator's recent history either.
Nothing on record ties , the wallet that funded this deployer, to a past rug on Robinhood Chain.
The funds were sent through a batch-send contract.
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.
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.
Bytecode did not match any known clone template.
Contract deployed 989h ago.
Launched on Pons V2 and graduated to a DEX pool.
Creator bought 0% of the raise. The pool's creation transaction could not be fully read this scan, so its launch buys are unknown.
Fingerprint UNKNOWN, but source is verified, so the code is readable by anyone.