Token Dashboard
tokens
3721
contracts
11709
confirmed
9939of 11709
chains
15
unmeasured
51
queued
0

AIW3 AIW3

2 contracts on 2 chains · 2 routes via LayerZero
status
liquid1 of 2 chains · warm
first bridged
2 mo ago2026-09-03 06:17
confirmed by a transfer
2 of 2every contract seen in a tx
already alerted
nothing yet
pins
3latest 2 mo ago

Contracts

binance canonical · via layerzero confirmed
0x37e94fc0…e8880b open
liquid1 bps · 0.01% via kyberswap5
Peer map: the protocol names this contract as a peerstrong +5
…
hyperevm canonical · via layerzero confirmed
0x7b3125f8…438da7 open
illiquidpools hold $0, under the floor3
Bridge registry lists itstrong +3
…

Routes

2 confirmed · 0 possible
LaneBridgeEvidenceProofLast seen
binance 0x37e94fc0…e8880b → hyperevm 0x7b3125f8…438da7 LayerZero confirmed 0xcb2bfaf1…4559a7 2 mo ago
hyperevm 0x7b3125f8…438da7 → binance 0x37e94fc0…e8880b LayerZero confirmed 0x9bfcb873…9f7ff2 2 mo ago

How it moves

LZ · 2 tx binanceliquid hyperevmilliquid
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-03 06:17 UTC · 2 mo ago · 2 contracts today
First pin received
2026-09-03 04:59 UTC · 2 mo ago · #5961 via layerzero
First liquid
2026-10-25 15:34 UTC · 2 min ago · a chain quoted liquid
First alert
needs a second liquid chain joined by a route, or the only contract on its chain — binance is liquid, hyperevm is not
All chains reported
none yet

Pins behind it

3
#8604binance → hyperevmskipped duplicate · 14 h#7636hyperevm → binanceskipped duplicate · 10 h#5961hyperevm → binancediscovered · 1 h 18 min