Token Dashboard
tokens
1960
contracts
6137
confirmed
5685 of 6137
chains seen
14
unmeasured
175
queued
0

CATTON

Catton AI
status
liquid2/2 checked · 1 liquid · warm
first bridged
35 h ago
arrived via
layerzero
contracts
3 on 2 chains
confirmed by a transfer
3 of 3
liquidity
2 of 2 chains checked · 1 liquid
checking
warm
already alerted on
nothing yet
pins
2

Lifecycle

  1. first pin received 2026-09-03 06:06:20 UTC · 2 d ago #7144 via layerzero
  2. token discovered 2026-09-03 10:03:43 UTC · 35 h ago 3 contracts today
  3. first liquid 2026-09-04 20:33:30 UTC · 10 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

More than one contract on solana (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

binance mint burn via layerzero decimals differ from source 5
0xcefc79c16cd62cf0c35c1d16d23b9f266f2eda51 open
liquid163 bps · 1.63% via kyberswap

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer+5{"tx":"5fMNbjyztZ3WBwu3b9HvL6275L8UwWkwmmefpWycyG4a8PP4sf8eWB1FdDKDLUbFgBEXrVVhoPYVVCEFpyeR9x4z","adapter":"layerzero"}
solana mint burn via layerzero decimals differ from source 5
7ZmoPE7DfMBkTkwQXXp2DMmx3qCY8H7kQrdSCcYHw7mZ open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer+5{"tx":"0x066eb85fe740495f82f30f4810d26082ae1eab03c043f0fd064956a98e83c80a","adapter":"layerzero"}
solana canonical via layerzero shadowed · not checked 8
EnYkmHKm13mLnBgpvHJZE2T6rqi8weQXoFuPccW9ZiD5 open
illiquidno route found

2 of 2 sources are protocol-attested — a contract confirmed this link.

registry+5{"tx":"5fMNbjyztZ3WBwu3b9HvL6275L8UwWkwmmefpWycyG4a8PP4sf8eWB1FdDKDLUbFgBEXrVVhoPYVVCEFpyeR9x4z","via":"solana_tx_parse"}
registry+3{"tx":"5fMNbjyztZ3WBwu3b9HvL6275L8UwWkwmmefpWycyG4a8PP4sf8eWB1FdDKDLUbFgBEXrVVhoPYVVCEFpyeR9x4z","from":"bridge_pin"}

How it moves between chains

Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.

from binance 1 of 1 reachable
solana layerzero 0x066eb85f… 35 h ago
from solana 1 of 1 reachable
binance layerzero W9rXBeEm9b… 35 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8402 2 d ago layerzerobinance → solana 0x15c6dd12…479e36 SKIPPED_DUPLICATE 13 h
#7144 2 d ago layerzerosolana → binance 5fMNbjyztZ…eR9x4z DISCOVERED 3 h 58 min

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.