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