Token Dashboard
tokens
2818
contracts
8329
confirmed
5710 of 8329
chains seen
14
unmeasured
142
queued
0

MON

MON
status
liquid4/4 checked · 1 liquid · warm
first bridged
2 d ago
arrived via
layerzero
contracts
5 on 4 chains
confirmed by a transfer
5 of 5
liquidity
4 of 4 chains checked · 1 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-03 06:07:53 UTC · 2 d ago #8694 via layerzero
  2. token discovered 2026-09-03 00:50:34 UTC · 2 d ago 5 contracts today
  3. first liquid 2026-09-05 06:55:44 UTC · 2 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

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

arbitrum mint burn via layerzero 5
0xfc87d55bc8bf441abfc24d04b2068a8f77bcfcc0same 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":"0x92a19b9e9fc3c0060fb74686a1c97e63e445198ebe2170c9635b268b07d18e7f","adapter":"layerzero"}
avalanche mint burn via layerzero 5
0x6063c12e10de94f1c421c0bdade394ebd3886b34 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":"0x3bd7ff411c8cb9f8cb969506b43992d6f9fe73f225e2f79fbdb9b4277a294bae","adapter":"layerzero"}
avalanche mint burn via layerzero shadowed · not checked 5
0xfc87d55bc8bf441abfc24d04b2068a8f77bcfcc0same open
illiquidpools hold $2, under the floor

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

bridge_transfer+5{"tx":"0x48423c8aca74b210c86c99b116f7777a334a95a4fb73096bdcaf0cb3fe145b2e","adapter":"layerzero"}
base mint burn via layerzero 5
0xfc87d55bc8bf441abfc24d04b2068a8f77bcfcc0same 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":"0x5af1770f74672705c080a4df1933b7370b1e7713f29e5c3ff397630b8db6ff24","adapter":"layerzero"}
ethereum canonical via layerzero 3
0xc555d625828c4527d477e595ff1dd5801b4a600e open
liquid70 bps · 0.70% via kyberswap

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

registry+3{"tx":"0x92a19b9e9fc3c0060fb74686a1c97e63e445198ebe2170c9635b268b07d18e7f","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 3 reachable
ethereum layerzero 0xf71ba4e1… 2 d ago
show 2 unreachable hide unreachable
avalanche no transfer seen
base no transfer seen
from avalanche 2 of 3 reachable
arbitrum layerzero 0x354f13ae… 2 d ago
ethereum layerzero 0x3bd7ff41… 34 h ago
show 1 unreachable hide unreachable
base no transfer seen
from base 1 of 3 reachable
ethereum layerzero 0x5af1770f… 2 d ago
show 2 unreachable hide unreachable
arbitrum no transfer seen
avalanche no transfer seen
from ethereum 3 of 3 reachable
arbitrum layerzero 0x92a19b9e… 2 d ago
avalanche layerzero 0xfe6134d1… 2 d ago
base layerzero 0x01900dc0… 2 d ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#8694 2 d ago layerzeroavalanche → ethereum 0x6e231ff1…1e5777 SKIPPED_DUPLICATE 14 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.