OORT

status: illiquid2/2 checked · 0 liquid · warm
first bridged: 3 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

first pin received 2026-09-03 06:06:41 UTC · 2 d ago #7481 via layerzero
token discovered 2026-09-02 22:15:00 UTC · 3 d ago 2 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none yet

Where this token lives

binance mint burn 5

0x5651fa7a726b9ec0cad00ee140179912b6e73599same open

illiquidpools hold $1, under the floor

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

same_address	+3	{"chain":"binance"}
codehash	+2	{"codehash":"0x5e4dcb0bb1910f6429e5fe91678990088a51c6d1cfe1b31d05fb9d948cc7867c"}

ethereum canonical via layerzero 3

0x5651fa7a726b9ec0cad00ee140179912b6e73599same open

illiquidpools hold $0, under the floor

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

registry

{"tx":"0xc400386d407ff23332855326a73beafa1edbfdcfb45e5eefb9caf49c95a5ae1f","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

ethereum layerzero 0xa158d63d… 2 d ago

from ethereum 1 of 1 reachable

binance layerzero 0xc400386d… 3 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7481	2 d ago	layerzerobinance → ethereum	0xa158d63d…0e6030	SKIPPED_DUPLICATE	10 h

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