MON
MON
status liquid 4/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
Lifecycle
first pin received
2026-09-03 06:07:53 UTC · 2 d ago
#8694 via layerzero
token discovered
2026-09-03 00:50:34 UTC · 2 d ago
5 contracts today
first liquid
2026-09-05 06:55:44 UTC · 2 min ago
a chain quoted liquid
first alert
pending
not yet
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
copy
open
illiquid pools 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
copy
open
illiquid pools 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
copy
open
illiquid pools 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
copy
open
illiquid pools 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
copy
open
liquid 70 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
show 2 unreachable
hide unreachable
→
avalanche
no transfer seen
→
base
no transfer seen
from avalanche
2 of 3 reachable
show 1 unreachable
hide unreachable
from base
1 of 3 reachable
show 2 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
avalanche
no transfer seen
from ethereum
3 of 3 reachable
Pins behind this token
Pin Received Bridge Bridge tx Outcome Discovery took
#8694
2 d ago
layerzeroavalanche → ethereum
0x6e231ff1…1e5777
SKIPPED_DUPLICATE
14 h