ORCLd

Oracle (dStock)

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

Lifecycle

first pin received 2026-09-03 06:06:41 UTC · 2 d ago #7523 via layerzero
token discovered 2026-09-03 16:15:32 UTC · 2 d 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

0xca2156522638f597ffb3705857ffdc356efabe50 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

{"tx":"0x5fdca75c221d135ca54806ec76061e034d652aac343d23eae1031e8de454e782","adapter":"layerzero"}

binance canonical via layerzero 3

0x60ea90c96e83cf9c0fcbfe844b20410ee89fe4c5 open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0x5fdca75c221d135ca54806ec76061e034d652aac343d23eae1031e8de454e782","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 0x5fdca75c… 2 d ago

from hyperevm 1 of 1 reachable

binance layerzero 0x19c3f77f… 31 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8912	2 d ago	layerzerohyperevm → binance	0xb1b9835e…1593bd	SKIPPED_DUPLICATE	15 h
#7523	2 d ago	layerzerobinance → hyperevm	0x5fdca75c…54e782	DISCOVERED	10 h

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