0x1a07a58ba8e1f183d58c04f01da5cd57da7e320a
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xabf60ff2097cf6cfcbbd45cf626cb1db8d3d994413ed949b1cd79d6aaf47b326","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x852e896161931bb9f785bf75365927e70f47b988
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xabf60ff2097cf6cfcbbd45cf626cb1db8d3d994413ed949b1cd79d6aaf47b326","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 |
|---|---|---|---|---|---|
| #6362 | 2 d ago | base_bridgeethereum → base | 0xabf60ff2…47b326 | DISCOVERED | 1 h 23 min |
Every address above came from an on-chain read. The evidence trail shows which read produced it.