XYRO

status: fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged: 25 h ago
arrived via: ccip
contracts: 2 on 2 chains
confirmed by a transfer: 2 of 2
liquidity: 2 of 2 chains checked · 2 liquid
checking: hot
already alerted on: arbitrum, ethereum
pins: 2

Lifecycle

first pin received 2026-09-03 06:06:43 UTC · 36 h ago #7792 via ccip
token discovered 2026-09-03 16:48:03 UTC · 25 h ago 2 contracts today
first liquid 2026-09-04 03:40:43 UTC · 14 h ago a chain quoted liquid
first alert 2026-09-04 03:40:43 UTC · 14 h ago multi_chain_liquid, sent 14 h ago
reported chains arbitrum, ethereum — 2 of 2

Where this token lives

ethereum mint burn via ccip 5

0x4eddb15a0abfa2c349e8065af9214e942d9a6d36 open

liquidlast verified 14 h ago

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

bridge_transfer

{"tx":"0x37fd813fffea8a3ca53d5d50d2e510d3691e9fdd7162cfff63a5b343e8bee73d","adapter":"ccip"}

arbitrum canonical via ccip 3

0xaeac3b55c3522157ecda7ec8fcb86c832faa28af open

liquidlast verified 14 h ago

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

registry

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

ethereum ccip 0x37fd813f… 25 h ago

from ethereum 1 of 1 reachable

arbitrum ccip 0x7fa25b93… 24 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8268	36 h ago	ccipethereum → arbitrum	0x4700c1ef…f54e1b	SKIPPED_DUPLICATE	11 h
#7792	36 h ago	cciparbitrum → ethereum	0x37fd813f…bee73d	DISCOVERED	10 h

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	14 h ago	SENT	14 h ago	314

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