first pin received2026-09-06 14:01:06 UTC · 26 h ago#9426 via layerzero
token discovered2026-09-06 14:54:59 UTC · 25 h ago3 contracts today
first liquid2026-09-07 15:24:12 UTC · 8 min agoa chain quoted liquid
first alertpendingnot yet
reported chainspendingnone yet
Where this token lives
More than one contract on solana (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.
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.
{"tx":"4GAaCgALA5ECvvLwMoP3Z7HZASiaBKvQUkRs9GFpKxJopH5dGTbR4D8vtecuYfNWrjZZvwWUspERqzA6yVVminvJ","bridge":"layerzero","reason":"a delivered transfer connected contracts held by two assets","endpoint":
active
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.