No current verdict. The last complete check is from 2026-10-17 under an older formula (v1.60). A new check is underway.
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
—
This token's creator removed liquidity from this token's own pool: 1 withdrawal on Uniswap V4.
It closed the position completely.
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 52.5% 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. 5 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
Top 10 holders hold 50.0% of the circulating float.
On raw total supply that's 48.8%, because 2.5% 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 48.9% of the float on its own.
This exact contract code has been used by 30 other tokens, and 28 of them lost most of their value or had their liquidity removed (0xde19…5ee5, 0xa918…3f22, 0x37e9…a414).
That describes those tokens. It does not say who created this one.
Sell execution could not be established on the other venues checked: No simulated route could be definitively classified; the token-wide result is unresolved.
Sells on this pool go through a swap hook. The hook's owner is 0x71c8…97bc. Our code check found functions that let its owner set a router list, a whitelist or a blacklist. Whether the owner has used them is not something this scan can see. Its code is identical to a hook template we have seen on other tokens on this chain. Details are under Pool Hooks.
On that scan, 5 checks had missing or incomplete data. (Shortened from the original receipt.)
Deployer is a fresh wallet funded by another fresh wallet, the classic pre-rug setup.
These are gaps in what we could see, not problems found in this token.
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.
Pool creation time unavailable.
No canonical asset collision.
No scam tag on the explorer.
Nothing on record ties , the wallet that funded this deployer, to a past rug on Robinhood Chain.
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 partially verified on the explorer, matched from another address with identical bytecode rather than proven against this one.
The token contract has no mint, pause, blacklist or limit functions in its bytecode.
No fee or limit toggling by the deployer in the transactions searched.
This looks at the deployer's recent history only, so calls by a separate fee authority are out of its reach.
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 93h ago.
No launchpad deployed this token.
It was deployed directly. That counts neither for nor against it, so the on-chain checks decide this one.
Fingerprint UNKNOWN, but the source is partially verified (bytecode-database match), so the code is readable.
This token trades in V4 pools that run a hook, a contract that executes on swaps. Here is what Uniswap's public hook list says about each one. It describes the hook, not this token.
Its code is byte for byte the same as a hook template we have seen on other tokens on this chain.
Found by reading the hook's code. Whether the owner has used these controls is not something this scan can see.
We could not read Uniswap's hook list just now, so we cannot say whether this hook is described there.
Robinhood