Token Dashboard
tokens
2818
contracts
8328
confirmed
5710 of 8328
chains seen
14
unmeasured
181
queued
0

GLV [WETH-USDC]

GMX Liquidity Vault
status
illiquid5/5 checked · 0 liquid · cold
first bridged
2 d ago
arrived via
layerzero
contracts
5 on 5 chains
confirmed by a transfer
5 of 5
liquidity
5 of 5 chains checked · 0 liquid
checking
cold
already alerted on
nothing yet
pins
3

Lifecycle

  1. first pin received 2026-09-03 06:06:13 UTC · 2 d ago #6316 via layerzero
  2. token discovered 2026-09-03 06:52:42 UTC · 2 d ago 5 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

binance mint burn via layerzero 8
0x0bc5ab50fd581b34681a9be180179b1ef0b238c7same open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"binance"}
peer_map+5{"via":{"address":"0x0bc5ab50fd581b34681a9be180179b1ef0b238c7","chainSlug":"ethereum"},"adapter":"layerzero"}
arbitrum canonical via layerzero 5
0x528a5bac7e746c9a509a1f4f6df58a03d44279f9 open
illiquidpools hold $0, under the floor

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

peer_map+5{"via":{"address":"0x0bc5ab50fd581b34681a9be180179b1ef0b238c7","chainSlug":"ethereum"},"adapter":"layerzero","oftAdapter":"0x8c92eae643040ff0fb65b423433001c176cb0bb6","unwrappedTo":"0x528a5bac7e746c9a509a1f4f6df58a03d44279f9"}
base mint burn via layerzero 5
0x8c92eae643040ff0fb65b423433001c176cb0bb6same open
illiquidpools hold $0, under the floor

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

peer_map+5{"via":{"address":"0x0bc5ab50fd581b34681a9be180179b1ef0b238c7","chainSlug":"ethereum"},"adapter":"layerzero"}
bera mint burn via layerzero 5
0x8c92eae643040ff0fb65b423433001c176cb0bb6same open
illiquidpools hold $0, under the floor

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

peer_map+5{"via":{"address":"0x0bc5ab50fd581b34681a9be180179b1ef0b238c7","chainSlug":"ethereum"},"adapter":"layerzero"}
ethereum canonical via layerzero 3
0x0bc5ab50fd581b34681a9be180179b1ef0b238c7same open
illiquidpools hold $0, under the floor

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

registry+3{"tx":"0x71d50aa5efb7061ca41dba1be4e85bab23500bb40b4f6aefae4ae34118bf3683","from":"bridge_pin"}

How it moves between chains

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 4 of 4 reachable
base layerzero 0x248579ae… 2 d ago
bera layerzero 0xb375ed63… 2 d ago
binance layerzero 0x0dae43c9… 2 d ago
ethereum layerzero 0x4dae1718… 35 h ago
from base 4 of 4 reachable
arbitrum layerzero 0x541696e1… 2 d ago
bera layerzero 0x01ca130f… 2 d ago
binance layerzero 0x8f76b45f… 2 d ago
ethereum layerzero 0x26609eaf… 2 d ago
from bera 4 of 4 reachable
arbitrum layerzero 0x5bed2ce8… 2 d ago
base layerzero 0x7afb0be2… 2 d ago
binance layerzero 0xeaa940f0… 2 d ago
ethereum layerzero 0x663dd4ae… 2 d ago
from binance 4 of 4 reachable
arbitrum layerzero 0x9d75da28… 2 d ago
base layerzero 0xaaad1cf4… 2 d ago
bera layerzero 0x943bcb99… 2 d ago
ethereum layerzero 0xcbcefb7c… 2 d ago
from ethereum 4 of 4 reachable
arbitrum layerzero 0x71d50aa5… 2 d ago
base layerzero 0x3753e932… 2 d ago
bera layerzero 0x80a4a7cb… 2 d ago
binance layerzero 0xc505b8fe… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8273 2 d ago layerzeroarbitrum → ethereum 0x6468106e…f8644f SKIPPED_DUPLICATE 11 h
#7687 2 d ago layerzerobase → arbitrum 0xe50795b6…8dec98 SKIPPED_DUPLICATE 10 h
#6316 2 d ago layerzeroethereum → arbitrum 0x71d50aa5…bf3683 DISCOVERED 46 min

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.