2
5 contracts on 4 chains · 10 routes via LZLayerZero2 contracts on sonic. 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 ↓
base
mint burn · via layerzero
confirmed
0x194f360d…ea1624same
open
sonic
canonical · via layerzero
inferred
2 on this chain
0xb0f75832…caaa0b
open
sonic
mint burn · via layerzero
confirmed
2 on this chain
0x4e0037f4…6099e3
open
arbitrum
mint burn · via layerzero
confirmed
0x194f360d…ea1624same
open
ethereum
canonical · via layerzero
confirmed
0x194f360d…ea1624same
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
base 0x194f360d…ea1624 → sonic 0x4e0037f4…6099e3 |
LZLayerZero | confirmed | 0xd7473493…805fcf | 2 mo ago |
sonic 0x4e0037f4…6099e3 → base 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0x7d1764c0…1036cc | 2 mo ago |
arbitrum 0x194f360d…ea1624 → sonic 0x4e0037f4…6099e3 |
LZLayerZero | confirmed | 0x9e595f46…957451 | 2 mo ago |
arbitrum 0x194f360d…ea1624 → base 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0xc5b9a6da…fe1c0e | 2 mo ago |
base 0x194f360d…ea1624 → arbitrum 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0xd0f1e9b2…a7f222 | 2 mo ago |
sonic 0x4e0037f4…6099e3 → arbitrum 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0x40bb37f1…f501ec | 2 mo ago |
base 0x194f360d…ea1624 → ethereum 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0x565058fe…f695d0 | 2 mo ago |
ethereum 0x194f360d…ea1624 → base 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0x7d520baa…78e5ee | 2 mo ago |
arbitrum 0x194f360d…ea1624 → ethereum 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0xfb27556a…740374 | 2 mo ago |
ethereum 0x194f360d…ea1624 → arbitrum 0x194f360d…ea1624 |
LZLayerZero | confirmed | 0x42799bea…1fbb51 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.