0xdd16ec0f66e54d453e6756713e533355989040e4
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x042f909429d3d6085e122d69937ba8adec420913201a058cfc8b5dae78e8f5cb","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x4fb9b20dafe45d91ae287f2e07b2e79709308178
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x24f85a8fc98d7a3724bf9494d6e0ac9bde23a90a5965e566b9a0c26de644e825","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 |
|---|---|---|---|---|---|
| #7016 | 2 d ago | base_bridgeethereum → base | 0x042f9094…e8f5cb | DISCOVERED | 3 h 44 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 31 h ago | SENT | 31 h ago | 220 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.