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