Token Dashboard
tokens
1957
contracts
6128
confirmed
5678 of 6128
chains seen
14
unmeasured
174
queued
0

NRN

Neuron
status
illiquid2/2 checked · 0 liquid · warm
first bridged
20 h ago
arrived via
layerzero
contracts
2 on 2 chains
confirmed by a transfer
2 of 2
liquidity
2 of 2 chains checked · 0 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:07:55 UTC · 36 h ago #8944 via layerzero
  2. token discovered 2026-09-03 21:49:38 UTC · 20 h ago 2 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

base mint burn via layerzero 5
0x0147a160e0d691ebdc8e2eba22a477f049f05485 open
illiquidpools hold $0, under the floor

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

peer_map+5{"via":{"address":"0x0147a160e0d691ebdc8e2eba22a477f049f05485","chainSlug":"arbitrum"},"adapter":"layerzero"}
arbitrum canonical via layerzero 3
0xdadeca1167fe47499e53eb50f261103630974905 open
illiquidpools hold $233, under the floor

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

registry+3{"tx":"0xf4346f52593e6f1b07dca390cbf534a146f55da572595a87a8804be8e329476b","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 arbitrum 1 of 1 reachable
base layerzero 0xf4346f52… 20 h ago
from base 1 of 1 reachable
arbitrum layerzero 0xd4eb4900… 20 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8944 36 h ago layerzeroarbitrum → base 0xf4346f52…29476b DISCOVERED 15 h

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.