Token Dashboard
tokens
2788
contracts
8845
confirmed
7202 of 8845
chains seen
14
unmeasured
92
queued
0

DN2

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

Lifecycle

  1. first pin received 2026-09-06 13:59:22 UTC · 20 h ago #9318 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 2 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

hyperevm mint burn via layerzero
7
0xb130a7d12838d0acdf21ec2961d2a95749d52247 open
illiquidpools hold $0, under the floor

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

discord+2{"notes":[],"proven":true,"ticker":"DN2","source_tx":"0xd56a7e4c8b2a44ced19c79413749181bfb161e69afb9fe3f37aa9975b4c2a5ce","message_id":"1397112194264596581","message_ts":"2025-07-22T07:05:04","source_url":"https://layerzeroscan.com/tx/0xd56a7e4c8b2a44ced19c79413749181bfb161e69afb9fe3f37aa9975b4c2a5ce","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1397112194264596581","source_kind":"layerzero_tx","curator_liquidity":false}
peer_map+5{"via":{"address":"0x2a8e357623cd8bc36e69ba2f52a7d0a13c8bd0bb","chainSlug":"ethereum"},"adapter":"layerzero"}
ethereum canonical via layerzero
5
0x2a8e357623cd8bc36e69ba2f52a7d0a13c8bd0bb open
illiquidpools hold $0, under the floor

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

discord+2{"notes":[],"proven":true,"ticker":"DN2","source_tx":"0xd56a7e4c8b2a44ced19c79413749181bfb161e69afb9fe3f37aa9975b4c2a5ce","message_id":"1397112194264596581","message_ts":"2025-07-22T07:05:04","source_url":"https://layerzeroscan.com/tx/0xd56a7e4c8b2a44ced19c79413749181bfb161e69afb9fe3f37aa9975b4c2a5ce","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1397112194264596581","source_kind":"layerzero_tx","curator_liquidity":false}
registry+3{"tx":"0xd56a7e4c8b2a44ced19c79413749181bfb161e69afb9fe3f37aa9975b4c2a5ce","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 ethereum 1 of 1 reachable
hyperevm layerzero 0xd56a7e4c… 20 h ago
from hyperevm 0 of 1 reachable

No transfer has been seen leaving hyperevm.

show 1 unreachable hide unreachable
ethereum no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9318 20 h ago layerzeroethereum → hyperevm 0xd56a7e4c…c2a5ce DISCOVERED 9 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.