0x2162fdb116bc95d85b898bdae77e053ef0c36eaa
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xab67b567bbb3509570a46983b7205e9cc245103657dbd74e842109c8ff6bc0b2","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"arbitrum_bridge"} |
0x1d831888ce3b00d9c2c63a3b841a55e5de793813
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 |
|---|---|---|---|---|---|
| #8570 | 36 h ago | arbitrum_bridgeethereum → arbitrum | 0xab67b567…6bc0b2 | DISCOVERED | 14 h |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 11 h ago | SENT | 11 h ago | 642 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.