first pin receivedpendingno pin linked (added by hand, or before pins were tracked)
token discovered2026-09-05 12:33:06 UTC · 2 d ago3 contracts today
first liquidpendingnot yet
first alertpendingnot yet
reported chainspendingnone yet
Where this token lives
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.
binancecanonicalvia ccippotential · no transfer seen2
No bridge transaction yet. These contracts are inferred, not confirmed by a transfer. Paste a bridge transaction that moved this token and discovery re-checks every contract and maps its routes.
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.
from binance0 of 1 reachable
No transfer has been seen leaving binance.
show 1 unreachablehide unreachable
→polygonno transfer seen
from polygon0 of 1 reachable
No transfer has been seen leaving polygon.
show 1 unreachablehide unreachable
→binanceno transfer seen
Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.
Every address above came from an on-chain read. The evidence trail shows which read produced it.