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