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