Trade with care. Read the warnings first.
We couldn't finish the sell test on the other exchanges we checked.
Scanned 2d ago. Scan again before you trade.
- WARNHoneypot
- WARNChecks with missing data
- WARNHolder concentration
DexProof recorded funcat as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1381 published 28 Oct 2026 (UTC). Of 28 checks, 16 passed, 3 warned and 9 could not be run.
Trade with care. Read the warnings first.
We couldn't finish the sell test on the other exchanges we checked.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
We couldn't finish the sell test on the other exchanges we checked.
At least one pool did not pass its sell test and could not be shown too small to matter, so we can't say this token can be sold everywhere. Sells on this pool go through a swap hook we could not verify. Our code check found no owner-set sell controls, but that does not show what the hook does to a sale.
We couldn't read some checks on this scan, so the verdict is limited.
A failed read is not a clean result. This describes what we could see, not the token.
Top 10 holders hold 47% of the tokens in circulation.
The largest holder is , a plain wallet, holding 8.6% of the tokens in circulation on its own. Against total supply, the top 10 hold 21.3%. Liquidity pools hold 54.6% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades.
These are gaps in what we could see, not problems found in this token.
We can't rule out that the creator pulled liquidity from this token's pool.
We didn't check 602 transactions by the creator that could remove liquidity.
We didn't trace where the creator's wallet got its funds, so we couldn't check for past rugs.
We didn't trace where this deployer's money came from, so we can't say if it links to a known rugger.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
A contract created this token, so we can't see the person behind it.
So we can't check whether it changed fees or limits.
We could not find when this token's pool was created.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This token has no pump-and-dump mark in our records.
100.0% of this V4 pool's liquidity is locked in positions under the pool's own launch hook.
That hook rejects every attempt to remove liquidity. The hook cannot be upgraded, so this liquidity can never be withdrawn. This pool is on Uniswap V4 and holds 98.9% of the liquidity we could read. 2 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
This deployer has no earlier launches on record.
The contract has no owner function, so it has no single owner wallet.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is verified on the explorer.
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code. This is about the token contract only. Its main pool runs a hook that can change what a trade pays out, and we have not established a limit on it.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This token's code doesn't match any code template we know of.
This contract was 110 days old at this scan.
Launched on letscash.fun, which puts tokens straight into an exchange pool and runs no bonding curve.
So there was no raise for the creator to buy into.
The source is verified, so anyone can read the code.
We could not match it to a known template.