Token Dashboard
tokens
2780
contracts
8798
confirmed
7155 of 8798
chains seen
14
unmeasured
91
queued
0

RADAR

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

Lifecycle

  1. first pin received 2026-09-03 06:06:14 UTC · 4 d ago #6521 via layerzero
  2. token discovered 2026-09-02 21:53:11 UTC · 4 d ago 3 contracts today
  3. first liquid 2026-09-04 15:45:53 UTC · 2 d ago a chain quoted liquid
  4. first alert 2026-09-04 05:11:58 UTC · 3 d ago multi_chain_liquid, sent 3 d ago
  5. reported chains binance, ethereum, polygon — 3 of 3

Where this token lives

polygon mint burn via layerzero
5
0xdcb72ae4d5dc6ae274461d57e65db8d50d0a33ad open
liquidlast verified 2 d ago

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

bridge_transfer+5{"tx":"0x4b4ced7e4dc9f8fbb495df77f5f0c79f31a2cdedf153024e003f3ecdd969bc5c","adapter":"layerzero"}
binance mint burn via layerzero
5
0x489580eb70a50515296ef31e8179ff3e77e24965 open
liquidlast verified 2 d ago

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

bridge_transfer+5{"tx":"0xd9eac5db2fe3bf140173217b67defafe7c88089940235b9aabd1f0b41c35d9d2","adapter":"layerzero"}
ethereum canonical via layerzero
3
0x44709a920fccf795fbc57baa433cc3dd53c44dbe open
liquidlast verified 2 d ago

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

registry+3{"tx":"0x4b4ced7e4dc9f8fbb495df77f5f0c79f31a2cdedf153024e003f3ecdd969bc5c","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 2 of 2 reachable
ethereum layerzero 0xc6bde453… 4 d ago
polygon layerzero 0xe3ae678e… 4 d ago
from ethereum 2 of 2 reachable
binance layerzero 0xd9eac5db… 4 d ago
polygon layerzero 0x4b4ced7e… 4 d ago
from polygon 2 of 2 reachable
binance layerzero 0x5a15d90b… 3 d ago
ethereum layerzero 0x2f4c57cb… 4 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#7013 4 d ago layerzeropolygon → binance 0xb62dccb7…65fc3e SKIPPED_DUPLICATE 3 h 43 min
#6521 4 d ago layerzerobinance → polygon 0x4db63f2c…2e96f3 SKIPPED_DUPLICATE 2 h 9 min

Alerts

KindCreatedStateSentTelegram id
resend7 h ago SENT 7 h ago1141
chain_added2 d ago SENT 2 d ago766
multi_chain_liquid3 d ago SENT 3 d ago337

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.