first pin received2026-09-03 06:06:42 UTC · 2 d ago#7727 via layerzero
token discovered2026-09-02 21:38:30 UTC · 2 d ago5 contracts today
first liquidpendingnot yet
first alertpendingnot yet
reported chainspendingnone yet
Where this token lives
More than one contract on ethereum (2), 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.
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.
{"tx":"0x30f7c0f4af91dae880c7ea10dbc21890625ded4ca7590b7647c86caa6063ca8a","bridge":"layerzero","reason":"a delivered transfer connected contracts held by two assets","endpoint":"hyperevm:0x13a81c5e8b
active
Every address above came from an on-chain read. The evidence trail shows which read produced it.