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

LSD

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

Lifecycle

  1. first pin received 2026-09-06 14:00:04 UTC · 20 h ago #9365 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d ago 2 contracts today
  3. first liquid 2026-09-07 10:22:07 UTC · just now a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

sonic canonical via layerzero
6
0xf520d737dc03e0dfb81350c6fd27479dd75db88d 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":"LSD","source_tx":null,"message_id":"1420426055457439866","message_ts":"2025-09-24T15:06:01","source_url":"https://layerzeroscan.com/address/0x4c7E7371e40B3F8c74DdA97E967A47eee6b0b38f","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420426055457439866","source_kind":"oft_address","curator_liquidity":true}
peer_map+5{"via":{"address":"0x4c7e7371e40b3f8c74dda97e967a47eee6b0b38f","chainSlug":"base"},"adapter":"layerzero","oftAdapter":"0x4c7e7371e40b3f8c74dda97e967a47eee6b0b38f","unwrappedTo":"0xf520d737dc03e0dfb81350c6fd27479dd75db88d"}
base canonical via layerzero
4
0x4c7e7371e40b3f8c74dda97e967a47eee6b0b38f open
liquid113 bps · 1.13% via kyberswap

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

discord+1{"notes":[],"proven":false,"ticker":"LSD","source_tx":null,"message_id":"1420426055457439866","message_ts":"2025-09-24T15:06:01","source_url":"https://layerzeroscan.com/address/0x4c7E7371e40B3F8c74DdA97E967A47eee6b0b38f","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1420426055457439866","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x1bbb46ad85def35e89efed521834ea02ea788d846f096cad6614b8e34b598dc8","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 base 1 of 1 reachable
sonic layerzero 0x1bbb46ad… 20 h ago
from sonic 1 of 1 reachable
base layerzero 0x5775f69a… 20 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9365 20 h ago layerzerobase → sonic 0x1bbb46ad…598dc8 DISCOVERED 14 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.