CLO (0x81d3…89d2) on BNB Chain: Danger

0x81d3a238b02827f62b9f390f947d36d4a5bf89d2

ChainK9 caught a trap when it traded this token on a private copy of the chain. Scanned 6 Nov 2026, 03:41 UTC at block 131938485 (full scan).

Failed checks

Market: uniswap-v4 (v4 pool traded), opened 22 Oct 2026, 20:20 UTC, by 0x4da204091938af1d9eac4dc2c66c6a52c6ba6a5c (its other launches) · explorer.

More traps caught on BNB Chain

The free verdict names what was flagged; what each check saw is in a paid scan. Scan it again or see the evidence.

ChainK9 reports what happened when it traded the token on a private copy of its blockchain at the block shown. That is evidence, not a guarantee: a token's owner can change its rules after the scan, and traps no check tests can be missed. Nothing here is financial advice; you trade at your own risk.

A watchdog for on-chain security. · Is this token a trap? · Follow the money. · Listening to the chains. · Token traps caught. · Honeypot checker. · Rug pull checker. · Do your own research. · Build with ChainK9. · Pricing. · How often ChainK9 catches a honeypot. · Terms of use · Privacy notice