0xa91c82b6933105c23298e631a0c1be751d239162
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xa081d42358dc6ea25bcf87adb78319ff4769c945cc32c38125234ac6af5d53e6","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x08eb45c0a7ec0dd112026ecc0e10169efbbc8e7f
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x2bf3b36df7581b153da20905e26a6f0de1807deecbeaf7fd53d39196529b935c","adapter":"base_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 base.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #6846 | 2 d ago | base_bridgeethereum → base | 0xa081d423…5d53e6 | DISCOVERED | 3 h 10 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 14 h ago | SENT | 14 h ago | 694 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.