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