first pin receivedpendingno pin linked (added by hand, or before pins were tracked)
token discovered2026-09-02 22:14:43 UTC · 4 d ago4 contracts today
first liquid2026-09-06 17:51:21 UTC · 3 h agoa chain quoted liquid
first alert2026-09-02 22:39:31 UTC · 4 d agomulti_chain_liquid, sent 3 d ago
reported chainsethereum, solana — 2 of 3
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.
Every source here is an inference. A contract on this chain has not confirmed the link itself.
same_address
+3
{"chain":"binance"}
How it moves between chains
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
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.
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.