Token Dashboard
tokens
3706
contracts
11650
confirmed
9885of 11650
chains
15
unmeasured
50
queued
0

CT Concrete Token

2 contracts on 2 chains · 2 routes via LayerZero
status
illiquid2/2 checked · 0 liquid · warm
first bridged
25 d ago2026-09-30 05:34
confirmed by a transfer
2 of 2every contract seen in a tx
already alerted
nothing yet
pins
2latest 25 d ago
possible twin of CT #2804 +1

Contracts

ethereum mint burn · via layerzero confirmed
0xe3d89986…6d5308same open
illiquidpools hold $0, under the floor10
Same address as on another chainweak +3
Same bytecode as a known contractweak +2
Peer map: the protocol names this contract as a peerstrong +5
…
binance canonical · via layerzero confirmed
0xe3d89986…6d5308same open
illiquidpools hold $0, under the floor3
Bridge registry lists itstrong +3
…

Routes

2 confirmed · 0 possible
LaneBridgeEvidenceProofLast seen
ethereum 0xe3d89986…6d5308 → binance 0xe3d89986…6d5308 LayerZero confirmed 0x763a5ebb…3872bb 25 d ago
binance 0xe3d89986…6d5308 → ethereum 0xe3d89986…6d5308 LayerZero confirmed 0xfc6ae59c…6a3f63 25 d ago

How it moves

LZ · 2 tx binanceilliquid ethereumilliquid
transfer seen (moving)peer map onlyring = liquidity on that chain

Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.

from from the index ▾

Source chain

bridge LayerZero ▾

Bridge

Lifecycle

Token discovered
2026-09-30 05:34 UTC · 25 d ago · 2 contracts today
First pin received
2026-09-30 05:34 UTC · 25 d ago · #10879 via layerzero
First liquid
2026-10-01 08:43 UTC · 23 d ago · a chain quoted liquid
First alert
no chain is liquid yet
All chains reported
none yet

Pins behind it

2