Token Dashboard
tokens
2794
contracts
8865
confirmed
7220 of 8865
chains seen
14
unmeasured
103
queued
0

AVAX

name unknown
status
liquid2/2 checked · 1 liquid · hot
first bridged
3 d ago
arrived via
layerzero
contracts
2 on 2 chains
confirmed by a transfer
2 of 2
liquidity
2 of 2 chains checked · 1 liquid
checking
hot
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 14:02:09 UTC · 26 h ago #9482 via layerzero
  2. token discovered 2026-09-05 12:33:07 UTC · 2 d ago 2 contracts today
  3. first liquid 2026-09-07 15:34:36 UTC · 2 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

binance canonical via layerzero
6
0x1ce0c2827e2ef14d5c4f29a091d735a204794041 open
liquid35 bps · 0.35% via kyberswap

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

discord+1{"notes":[],"proven":false,"ticker":"AVAX","source_tx":null,"message_id":"1460495373360431255","message_ts":"2026-01-13T04:47:11","source_url":"https://layerzeroscan.com/address/0xE31Cd8f48Ab213596D58C6D83C8fbB8245B8FEd8","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1460495373360431255","source_kind":"oft_address","curator_liquidity":true}
peer_map+5{"via":{"address":"0xe31cd8f48ab213596d58c6d83c8fbb8245b8fed8","chainSlug":"sonic"},"adapter":"layerzero","oftAdapter":"0xe31cd8f48ab213596d58c6d83c8fbb8245b8fed8","unwrappedTo":"0x1ce0c2827e2ef14d5c4f29a091d735a204794041"}
sonic canonical via layerzero
4
0xe31cd8f48ab213596d58c6d83c8fbb8245b8fed8 open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"AVAX","source_tx":null,"message_id":"1460495373360431255","message_ts":"2026-01-13T04:47:11","source_url":"https://layerzeroscan.com/address/0xE31Cd8f48Ab213596D58C6D83C8fbB8245B8FEd8","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1460495373360431255","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x1fad5095655f98842140f4d07811793001a81ddbfaecd54c36b6c3651ccb3b69","from":"bridge_pin"}

How it moves between chains

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

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
sonic layerzero 0xc3dc05a8… 24 h ago
from sonic 1 of 1 reachable
binance layerzero 0x1fad5095… 24 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9482 26 h ago layerzerosonic → binance 0x1fad5095…cb3b69 DISCOVERED 1 h 40 min

Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.

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.