Token Dashboard
tokens
1962
contracts
6141
confirmed
5689 of 6141
chains seen
14
unmeasured
180
queued
0

PR

Primer
status
illiquid2/2 checked · 0 liquid · cold
first bridged
3 d ago
arrived via
layerzero
contracts
3 on 2 chains
confirmed by a transfer
3 of 3
liquidity
2 of 2 chains checked · 0 liquid
checking
cold
already alerted on
nothing yet
pins
0

Lifecycle

  1. first pin received pending no pin linked (added by hand, or before pins were tracked)
  2. token discovered 2026-09-02 04:55:11 UTC · 3 d ago 3 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

More than one contract on robinhood (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.

base canonical via layerzero 5
0x2357110f5f0c5344eef75966500c75116a4aa153 open
illiquidpools hold $0, under the floor

1 of 1 sources are protocol-attested — a contract confirmed this link.

peer_map+5{"via":{"address":"0x235767cc3d01ec18b5db87973975ac8616b2a153","chainSlug":"robinhood"},"adapter":"layerzero","oftAdapter":"0x01db67e285b0285ddb5b1bf75705ce2d79cc7e14","unwrappedTo":"0x2357110f5f0c5344eef75966500c75116a4aa153"}
robinhood mint burn via layerzero 5
0x11e0f916494cd7ee11de376ebe35243837427b92 open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer+5{"tx":"0xa8103c89f2c9b795337d2c477ae0b4fa093e661821dcf7e0d455dc309a988f70","adapter":"layerzero"}
robinhood canonical via layerzero shadowed · not checked 3
0x235767cc3d01ec18b5db87973975ac8616b2a153 open
illiquidpools hold $0, under the floor

1 of 1 sources are protocol-attested — a contract confirmed this link.

registry+3{"tx":"0xe67a4ff8cafbdb2d9080cb631dadb987d74210a3c347d4ea8b72449d674eb00b","from":"bridge_pin"}

How it moves between chains

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 base 1 of 1 reachable
robinhood layerzero 0xa8103c89… 3 d ago
from robinhood 1 of 1 reachable
base layerzero 0xe67a4ff8… 3 d ago

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.