0xdb7bcef68f1b6a7344722ce41c9dedb4400781b4
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x1ea106e64f31d6bb0b036d64bbbb621cc4924be1c1a48f7ac7a88d9f7e961a5f","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x1cdef79f86ce3223db7dda1d55a7000b2d4612a6
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x1ea106e64f31d6bb0b036d64bbbb621cc4924be1c1a48f7ac7a88d9f7e961a5f","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 |
|---|---|---|---|---|---|
| #8945 | 36 h ago | base_bridgeethereum → base | 0x1ea106e6…961a5f | DISCOVERED | 15 h |
Every address above came from an on-chain read. The evidence trail shows which read produced it.