0xdfa208bb0b811cfbb5fa3ea98ec37aa86180e668
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xc6ca600e16cd1196c5f79f204534e93a7411295dfd37f73ccdb1aa7ff824783c","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0xa0ff877e3d4f3a108b1b3d5eb3e4369301d2b2d7
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xba82c7543db38a72e57c7734f1b669f47dcba06772d6b5b012bc619aaeda8e55","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 |
|---|---|---|---|---|---|
| #7975 | 36 h ago | base_bridgeethereum → base | 0xc6ca600e…24783c | DISCOVERED | 11 h |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 22 h ago | SENT | 22 h ago | 278 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.