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