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