Token Dashboard
tokens
2815
contracts
8320
confirmed
5702 of 8320
chains seen
14
unmeasured
186
queued
0

PT-sUSDai-15OCT2026

PT Staked USDai 15OCT2026
status
illiquid2/2 checked · 0 liquid · cold
first bridged
2 d ago
arrived via
layerzero
contracts
3 on 2 chains
confirmed by a transfer
3 of 3
liquidity
2 of 2 chains checked · 0 liquid
checking
cold
already alerted on
nothing yet
pins
3

Lifecycle

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

Where this token lives

More than one contract on binance (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

arbitrum canonical via layerzero 8
0xb459db106f645d698e74027eef6019a26a0675cc open
illiquidpools hold $0, under the floor

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

registry+3{"tx":"0xd51079efae70ecf4303753c36de62f4be0d81a88659de8a788c645d077c2dcd1","from":"bridge_pin"}
peer_map+5{"via":{"address":"0x5e1f3971f1644dfa762b28d20aa949943e00eafe","chainSlug":"binance"},"adapter":"layerzero","oftAdapter":"0xc1b83fc56a8b193d054c19c8bd9fe785e7f0a524","unwrappedTo":"0xb459db106f645d698e74027eef6019a26a0675cc"}
binance mint burn via layerzero 5
0x1e798c7fce8b3cdce8950f8ff5a0c62f1dc7d532 open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer+5{"tx":"0xd51079efae70ecf4303753c36de62f4be0d81a88659de8a788c645d077c2dcd1","adapter":"layerzero"}
binance canonical via layerzero shadowed · not checked 3
0x5e1f3971f1644dfa762b28d20aa949943e00eafe open
illiquidpools hold $0, under the floor

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

registry+3{"tx":"0xb3d5b3cee5ec7cd8d3a4fe6b88a2571130a4d4a699e02535775ae4367ca9c71c","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 1 of 1 reachable
binance layerzero 0x5b89084f… 32 h ago
from binance 1 of 1 reachable
arbitrum layerzero 0x5c8c1c20… 32 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8687 2 d ago layerzerobinance → arbitrum 0xb3d5b3ce…a9c71c DISCOVERED 14 h
#8193 2 d ago layerzerobinance → arbitrum 0x5c8c1c20…ab86ce SKIPPED_DUPLICATE 11 h
#6881 2 d ago layerzeroarbitrum → binance 0xd51079ef…c2dcd1 DISCOVERED 3 h 20 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.