0xb0415d55f2c87b7f99285848bd341c367feac1ea
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x45c1985b6935dcf497e55b6eedde14922cc18f2fa2039540f17bbe074c621040","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x10d348ca3e8a8a9ce67c39ccaf2dd4f99bb19bd8
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xe12815d6c141abff71b98694bea4cf046647f25aa2507169566ec4ef18d3922e","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 |
|---|---|---|---|---|---|
| #7798 | 36 h ago | base_bridgeethereum → base | 0x45c1985b…621040 | DISCOVERED | 10 h |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 24 h ago | SENT | 24 h ago | 272 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.