0x09395a2a58db45db0da254c7eaa5ac469d8bdc85
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x62d25a78382b11480e4ff70f721bf796c189d66c02f2e9ed731741afc3967578","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x858c50c3af1913b0e849afdb74617388a1a5340d
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x89077b6a10d56ab6c94084982d7b842e84019f0ef31cc3cf350be41224571bb7","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 |
|---|---|---|---|---|---|
| #7205 | 2 d ago | base_bridgeethereum → base | 0x62d25a78…967578 | DISCOVERED | 4 h 5 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 15 h ago | SENT | 15 h ago | 648 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.