MSFTd

Microsoft (dStock)

status: illiquid2/2 checked · 0 liquid · cold
first bridged: 25 h 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: cold
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-03 06:07:53 UTC · 2 d ago #8589 via layerzero
token discovered 2026-09-03 20:34:56 UTC · 25 h ago 2 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

Where this token lives

hyperevm mint burn via layerzero 5

0x66520d8fd614487214a25af7babf27584f59f76b open

illiquidpools hold $0, under the floor

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

peer_map

{"via":{"address":"0xf0419d9aed5788d600e581bf550e6e948f0517d0","chainSlug":"binance"},"adapter":"layerzero"}

binance canonical via layerzero 3

0x2baf817a53efb81a4c193854cbc437163a253168 open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0x217e5ae8d268263b225a7d86ce57960469b4a26a2e9d4331784d75d280b7cb17","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 binance 1 of 1 reachable

hyperevm layerzero 0x217e5ae8… 25 h ago

from hyperevm 1 of 1 reachable

binance layerzero 0x3073613d… 25 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8589	2 d ago	layerzerobinance → hyperevm	0x217e5ae8…b7cb17	DISCOVERED	14 h

Every address above came from an on-chain read. The evidence trail shows which read produced it.