Don't trade this token.
Selling is blocked on this token's main pool and every other pool big enough to matter.
Scanned 4d ago. Scan again before you trade.
- FAILHoneypot
- FAILDeployer pulled liquidity
- FAILSource verification
DexProof recorded KENZO as CRITICAL on Robinhood Chain under formula v1.63, in verdict #1177 published 26 Oct 2026 (UTC). Of 28 checks, 10 passed, 6 warned, 4 failed and 8 could not be run.
Don't trade this token.
Selling is blocked on this token's main pool and every other pool big enough to matter.
Scanned 4d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Selling is blocked on this token's main pool and every other pool big enough to matter.
This token's creator removed liquidity from this token's pool.
It made 1 withdrawal on Uniswap V2, and that withdrawal closed the position completely.
This contract's source code is not verified on the explorer.
The token contract has privileged functions (trading gate), and we couldn't confirm its ownership was given up.
Either an owner is still active, or we couldn't read one.
This token crashed after launch.
On 2026-10-13, its price or liquidity fell 95% or more below its 72-hour peak, and a second data source confirmed it. This often happens when early buyers sell. On its own it does not mean the contract or its liquidity is unsafe.
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.
The largest LP holder, (a contract), holds 100.0% of this pool's liquidity.
It is not the deployer. This contract is not a trusted locker, so this liquidity is not considered locked. Its controller or contract code may still move or withdraw it. The contract needs an audit before we can say more. None of this pool's liquidity is burned or locked.
This contract still has an active owner: .
The deployer changed fee or limit settings 1 time on this contract.
The source is not verified, so the code can't be read.
We could not match it to a known template.
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.
We could not find when this token's pool was created.
Launched on an unregistered launchpad, but we don't know how that launchpad works, so we can't say whether there was a raise for the creator to buy into.
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 deployer has no earlier launches on record.
Top 10 holders hold 17% of the tokens in circulation.
Against total supply, the top 10 hold 15.8%. Liquidity pools hold 6.9% 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.
This contract's code is fixed.
We found no standard upgrade setup on it.
No paid promotion found on DexScreener.
This token's code doesn't match any code template we know of.
This contract was 18 days old at this scan.