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

USDL

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 14:00:06 UTC · 20 h ago #9367 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

avalanche canonical via layerzero
6
0xc1303e1e2f204f16c7493214c66b4d34eeba2f2d 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":"USDL","source_tx":null,"message_id":"1420427229304848424","message_ts":"2025-09-24T15:10:41","source_url":"https://layerzeroscan.com/address/0x99E5BB6D3EE6cC6FdCb9fFA413cEcE2CB3Bfa749","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420427229304848424","source_kind":"oft_address","curator_liquidity":false}
peer_map+5{"via":{"address":"0xf410b11a6a00dbc51bf9f86785b3c0f1e6187c91","chainSlug":"base"},"adapter":"layerzero","oftAdapter":"0x99e5bb6d3ee6cc6fdcb9ffa413cece2cb3bfa749","unwrappedTo":"0xc1303e1e2f204f16c7493214c66b4d34eeba2f2d"}
base canonical via layerzero
4
0xf410b11a6a00dbc51bf9f86785b3c0f1e6187c91 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":"USDL","source_tx":null,"message_id":"1420427229304848424","message_ts":"2025-09-24T15:10:41","source_url":"https://layerzeroscan.com/address/0x99E5BB6D3EE6cC6FdCb9fFA413cEcE2CB3Bfa749","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420427229304848424","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x0db95692130a8bf5e018d0af9934ccb5dccecfd85d29e743f51af76627c4f60b","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 avalanche 1 of 1 reachable
base layerzero 0x1d1371ab… 20 h ago
from base 1 of 1 reachable
avalanche layerzero 0x0db95692… 20 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9367 20 h ago layerzerobase → avalanche 0x0db95692…c4f60b DISCOVERED 15 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.