0x031de51f3e8016514bd0963d0b2ab825a591db9a
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x10a2e9c56883566c83dcd66b9cf99f70a92a6209dba8d7252495d0e1b1fec1bb","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"arbitrum_bridge"} |
0x3b8db18e69d6686ad9371a423afe3dd1065c94f1
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"calculateL2TokenAddress","router":"0x72ce9c846789fdb6fc1f34ac4ad25dd9ef7031ef","adapter":"arbitrum_bridge"} |
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.
No transfer has been seen leaving arbitrum.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #8151 | 36 h ago | arbitrum_bridgeethereum → arbitrum | 0x10a2e9c5…fec1bb | DISCOVERED | 11 h |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 11 h ago | SENT | 11 h ago | 624 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.