More than one contract on binance (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.
0xba12bc7b210e61e5d3110b997a63ea216e0e18f7same
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"binance"} |
| codehash | +2 | {"codehash":"0x51cc14784ec84b6b017c99ad60a7531b87362b0239218e8e0f4c8cdd89cbbc36"} |
0xc32cc70741c3a8433dcbcb5ade071c299b55ffc8
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xc6a6d885283c135690f7a173c785f966e82528b733ce7ca6845ffc61d5115372","adapter":"layerzero"} |
0xba12bc7b210e61e5d3110b997a63ea216e0e18f7same
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xc6a6d885283c135690f7a173c785f966e82528b733ce7ca6845ffc61d5115372","from":"bridge_pin"} |
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.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #7876 | 36 h ago | layerzerobinance → base | 0x097cbae0…0079a9 | SKIPPED_DUPLICATE | 10 h |
| #7838 | 36 h ago | layerzerobase → binance | 0xc6a6d885…115372 | DISCOVERED | 10 h |
Every address above came from an on-chain read. The evidence trail shows which read produced it.