0x1c00c3e03c3a10a0c1d9b6d1a42e797d7cb4147a
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x3bc23fa4676133f414d480e104d86c56ff85e53bd26c00337f74be9be7976fa2","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0xdd177b9086c0f781380c4e5d7a3109cc85977acf
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x28b0b32f63f1f69411793ef250dfe9fdcf48a437e0398234edf9d61197818e27","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 |
|---|---|---|---|---|---|
| #9138 | 11 h ago | base_bridgeethereum → base | 0x3bc23fa4…976fa2 | DISCOVERED | 3 s |
Every address above came from an on-chain read. The evidence trail shows which read produced it.