3
4 contracts on 2 chains · 3 routes via LZLayerZero3 contracts on avalanche. A wrapper beside the canonical is normal; a clone reusing the ticker looks the same. The one a transfer confirmed outranks the one matched by symbol. Compare below ↓
ethereum
canonical · via layerzero
confirmed
0x9cf0ed01…14dad6
open
avalanche
canonical · via layerzero
confirmed
3 on this chain
0x71a022fc…a97cb1
open
avalanche
canonical
confirmed
3 on this chain
0x95daf2af…0cf786
open
avalanche
mint burn · via layerzero
inferred
3 on this chain
0xbefb3604…e7c454
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x9cf0ed01…14dad6 → avalanche 0x95daf2af…0cf786 |
LZLayerZero | confirmed | 0x7ebd5e92…bfb580 | 2 mo ago |
avalanche 0x95daf2af…0cf786 → ethereum 0x9cf0ed01…14dad6 |
LZLayerZero | confirmed | 0x328fad6c…2da319 | 2 mo ago |
ethereum 0x9cf0ed01…14dad6 → avalanche 0x71a022fc…a97cb1 |
LZLayerZero | confirmed | 0x6d0d5bb8…b5f990 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.