2 contracts on binance, 2 contracts on base. 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
2 on this chain
added
0xab1e131c…497191
open
base
mint burn
confirmed
2 on this chain
0x94482429…063092same
open
ethereum
mint burn · via layerzero
confirmed
added
0x94482429…063092same
open
binance
canonical · via layerzero
confirmed
2 on this chain
added
0x94482429…063092same
open
binance
mint burn · via layerzero
confirmed
2 on this chain
0x7f41fa46…c437e4
open
0x5e7a0591…58e8a2strong +5
arbitrum
mint burn · via layerzero
confirmed
0xca834fae…f4e58e
open
0xe6f1c56f…ee6c1dstrong +5| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
arbitrum 0xca834fae…f4e58e → binance 0x7f41fa46…c437e4 |
LZLayerZero | confirmed | 0x5e7a0591…58e8a2 | 2 mo ago |
arbitrum 0xca834fae…f4e58e → base 0x94482429…063092 |
LZLayerZero | confirmed | 0xe6f1c56f…ee6c1d | 2 mo ago |
base 0xab1e131c…497191 → ethereum 0x94482429…063092 |
LZLayerZero | confirmed | 0xc2d0bb96…73d58c | 2 mo ago |
ethereum 0x94482429…063092 → base 0xab1e131c…497191 |
LZLayerZero | confirmed | 0x149a11ec…95aa58 | 2 mo ago |
binance 0x94482429…063092 → ethereum 0x94482429…063092 |
LZLayerZero | confirmed | 0xaabb595f…e131bf | 2 mo ago |
base 0xab1e131c…497191 → binance 0x94482429…063092 |
LZLayerZero | confirmed | 0x93762dd1…077334 | 2 mo ago |
binance 0x94482429…063092 → base 0xab1e131c…497191 |
LZLayerZero | confirmed | 0x9118a82a…b38830 | 2 mo ago |
ethereum 0x94482429…063092 → binance 0x94482429…063092 |
LZLayerZero | confirmed | 0x11cbece4…00d9ae | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.