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
DexProof recorded FLTCH as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1365 published 28 Oct 2026 (UTC). Of 28 checks, 18 passed, 2 warned and 8 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.
These are gaps in what we could see, not problems found in this token.
We couldn't tell who funded the creator's wallet.
The funding contract, or the wallet behind it, could not be identified, so its history is unknown.
We couldn't identify the contract that funded this deployer or who sent it, so we can't say which wallets are linked to them.
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.
No liquidity removal by the wallet recorded as this token's creator from its own pool.
The creator's recent history has no removal calls either.
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 Launchpad V2 Launch Locker, a trusted locker contract.
The lock is permanent, so that liquidity can never be withdrawn. This pool is on Uniswap V4 and holds 100.0% of the liquidity we could read. One other pool charges a fee too large to trade through, so nothing a holder owns is at risk there.
This deployer has no earlier launches on record.
Top 10 holders hold 27% of the tokens in circulation.
Against total supply, the top 10 hold 3.8%. Liquidity pools hold 86.0% 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.
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, but it was matched from another address with identical bytecode, not proven against this one.
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 the Pons V2 Meme Hook, which can take up to 10% of each trade.
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 57 days old at this scan.
Launched on Pons V2 and graduated to a DEX pool.
The trades on its curve were not recorded, so how much of the raise the creator bought is unknown. We couldn't fully read the transaction that opened this token's pool, so we don't know who bought at launch.
The source is verified, so anyone can read the code.
We could not match it to a known template.