Token Dashboard
tokens
2792
contracts
8856
confirmed
7212 of 8856
chains seen
14
unmeasured
105
queued
0

v0G

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:05 UTC · 25 h ago #9425 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

arbitrum canonical via layerzero
6
0x5e95358b73bafe88c8dc1350697c4cb2354c63cd 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":"v0G","source_tx":null,"message_id":"1441689377624424499","message_ts":"2025-11-22T07:18:52","source_url":"https://layerzeroscan.com/address/0x0565FE63579760944f19b0932CB0EA36944a625C","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1441689377624424499","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0x0565fe63579760944f19b0932cb0ea36944a625c","chainSlug":"binance"},"adapter":"layerzero","oftAdapter":"0x33c42e171cfd7ec85d3db34d7f6d3d8121f64e63","unwrappedTo":"0x5e95358b73bafe88c8dc1350697c4cb2354c63cd"}
binance canonical via layerzero
4
0x0565fe63579760944f19b0932cb0ea36944a625c 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":"v0G","source_tx":null,"message_id":"1441689377624424499","message_ts":"2025-11-22T07:18:52","source_url":"https://layerzeroscan.com/address/0x0565FE63579760944f19b0932CB0EA36944a625C","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1441689377624424499","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x1a93268e6cbff3304c0324ca9fc24e37772682acaae68e2423ad3262400e5335","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 arbitrum 1 of 1 reachable
binance layerzero 0x5e42c1e6… 24 h ago
from binance 1 of 1 reachable
arbitrum layerzero 0x1a93268e… 24 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9425 25 h ago layerzerobinance → arbitrum 0x1a93268e…0e5335 DISCOVERED 54 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.