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