Token Dashboard
tokens
2818
contracts
8328
confirmed
5710 of 8328
chains seen
14
unmeasured
178
queued
0

CAT

Catcoin
status
partly reported3/3 checked · 2 liquid · 2 reported · hot
first bridged
2 d ago
arrived via
portal_bridge
contracts
4 on 3 chains
confirmed by a transfer
3 of 4
liquidity
3 of 3 chains checked · 2 liquid
checking
hot
already alerted on
binance, ethereum
pins
0

Lifecycle

  1. first pin received pending no pin linked (added by hand, or before pins were tracked)
  2. token discovered 2026-09-02 22:20:46 UTC · 2 d ago 4 contracts today
  3. first liquid 2026-09-04 06:10:38 UTC · 23 h ago a chain quoted liquid
  4. first alert 2026-09-04 06:10:38 UTC · 23 h ago multi_chain_liquid, sent 23 h ago
  5. reported chains binance, ethereum — 2 of 3

Where this token lives

More than one contract on ethereum (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 canonical via portal_bridge 8
0x59f4f336bf3d0c49dbfba4a74ebd2a6ace40539asame open
liquidlast verified 23 h ago

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

registry+3{"tx":"0xec80f6cdf050dc0f4cb33d9dc282c6aefd8bc4067b4482b388cbc3ffe4f1bafe","from":"bridge_pin"}
derivation+5{"via":"origin_from_index","adapter":"portal_bridge","originChainId":4}
ethereum mint burn potential · no transfer seen 5
0x59f4f336bf3d0c49dbfba4a74ebd2a6ace40539asame open
liquidlast verified 23 h ago

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

same_address+3{"chain":"ethereum"}
codehash+2{"codehash":"0x6ac913439c1c74e794a62468f323dd463b65a0e1a4f2d63d7eb970bfcc2a35db"}
ethereum lock mint wrapper via portal_bridge shadowed · not checked 5
0xba4442aabb56eb9d5d8ef89d1335552fa14d3768 open
liquidlast verified 25 h ago

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

derivation+5{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x3ee18b2214aff97000d974cf647e7c347e8fa585","originChainId":4}
solana lock mint wrapper via portal_bridge decimals differ from source 5
3QCPUFnnyaq2ikgKtpuALUDWs2WRqtXx9oHmcod6viML open
illiquidpools hold $0, under the floor

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

derivation+5{"via":"wrapped_mint_pda","adapter":"portal_bridge","originChainId":4}

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 2 of 2 reachable
ethereum portal_bridge 0xc11f5acd… 2 d ago
solana portal_bridge 0xec80f6cd… 2 d ago
from ethereum 2 of 2 reachable
binance portal_bridge 0x4d6e9352… 2 d ago
solana portal_bridge 0x326b26f7… 2 d ago
from solana 1 of 2 reachable
binance portal_bridge 2kCtkELAUa… 2 d ago
show 1 unreachable hide unreachable
ethereum no transfer seen

Alerts

KindCreatedStateSentTelegram id
multi_chain_liquid23 h ago SENT 23 h ago568

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.