Token Dashboard
tokens
2794
contracts
8865
confirmed
7214 of 8865
chains seen
14
unmeasured
104
queued
1

OWL

name unknown
status
illiquid2/2 checked · 0 liquid · warm
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 · 0 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 14:01:54 UTC · 26 h ago #9471 via layerzero
  2. token discovered 2026-09-05 12:33:07 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

ethereum canonical via layerzero
9
0x0e0693ea7acad160a1a778948da239748b22522b open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"OWL","source_tx":null,"message_id":"1457941839087927460","message_ts":"2026-01-06T03:40:21","source_url":"https://layerzeroscan.com/address/0x06Da145364eAeB2feB3ABA01e0d96Ee0c79f46a0","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1457941839087927460","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0xe50f04d3204a48ce0777f5de12b87d8cfea6078f06c39dd62078dd77b89f3d2c","from":"bridge_pin"}
registry+5{"via":"OFTAdapter.token","adapter":"layerzero","oftAdapter":"0x06da145364eaeb2feb3aba01e0d96ee0c79f46a0"}
binance mint burn via layerzero
6
0x1b25b7438d56dc3b8ffa1ea2c0663832e65ef99e 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":"OWL","source_tx":null,"message_id":"1457941839087927460","message_ts":"2026-01-06T03:40:21","source_url":"https://layerzeroscan.com/address/0x06Da145364eAeB2feB3ABA01e0d96Ee0c79f46a0","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1457941839087927460","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x06da145364eaeb2feb3aba01e0d96ee0c79f46a0","chainSlug":"ethereum"},"adapter":"layerzero"}

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 0 of 1 reachable

No transfer has been seen leaving binance.

show 1 unreachable hide unreachable
ethereum no transfer seen
from ethereum 1 of 1 reachable
binance layerzero 0xe50f04d3… 25 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9471 26 h ago layerzeroethereum → binance 0xe50f04d3…9f3d2c DISCOVERED 1 h 1 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.