2
3 contracts on 2 chains · 3 routes via LZLayerZero2 contracts on binance. 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 ↓
binance
mint burn · via layerzero
confirmed
2 on this chain
added
0xb0f09ea9…a30e37
open
0x9c952003…1a1f2cstrong +5binance
mint burn
confirmed
2 on this chain
0x951f086a…afeb5esame
open
ethereum
canonical · via layerzero
confirmed
added
0x951f086a…afeb5esame
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
binance 0xb0f09ea9…a30e37 → ethereum 0x951f086a…afeb5e |
LZLayerZero | confirmed | 0x3fea3a1d…cc12ba | 2 mo ago |
ethereum 0x951f086a…afeb5e → binance 0xb0f09ea9…a30e37 |
LZLayerZero | confirmed | 0x9c952003…1a1f2c | 2 mo ago |
ethereum 0x951f086a…afeb5e → binance 0x951f086a…afeb5e |
LZLayerZero | confirmed | 0x9c952003…1a1f2c | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
binance → ethereumskipped duplicate · 15 h#8789ethereum → binanceskipped duplicate · 15 h#5234ethereum → binanceskipped duplicate · 2 h 49 min#5171binance → ethereumskipped duplicate · 2 h 48 min#5170binance → ethereumskipped duplicate · 2 h 48 min#5169binance → ethereumskipped duplicate · 2 h 48 min#5155ethereum → binanceskipped duplicate · 2 h 48 min#3550ethereum → binanceskipped duplicate · 5 h 31 min| Kind | Created | State | Sent | Rechecks | Outcome | Telegram |
|---|---|---|---|---|---|---|
| resend | 2 mo ago | SENT | 2 mo ago | 0 | — | 1377 |
| multi_chain_liquid | 2 mo ago | SENT | 2 mo ago | 0 | — | 699 |