0xa1f410f13b6007fca76833ee7eb58478d47bc5ef
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x788af4f280ce3853dc628c5a06022da4bf20dbca8b98c709e48f5fdd93058256","adapter":"layerzero"} |
0x602b6c6cce5f95c00603bd07d8fa7ebaf3747d44
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x788af4f280ce3853dc628c5a06022da4bf20dbca8b98c709e48f5fdd93058256","from":"bridge_pin"} |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
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.
Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.
Every address above came from an on-chain read. The evidence trail shows which read produced it.