Token Dashboard
tokens
2792
contracts
8855
confirmed
7211 of 8855
chains seen
14
unmeasured
104
queued
0

MMM

name unknown
status
illiquid2/2 checked · 0 liquid · warm
first bridged
3 d 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-06 14:00:59 UTC · 24 h ago #9418 via layerzero
  2. token discovered 2026-09-05 12:33:06 UTC · 2 d 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 canonical via layerzero
9
0x23c60095553f0d6ec2ab58631b4724d151d45309same open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"MMM","source_tx":null,"message_id":"1440195207261065369","message_ts":"2025-11-18T04:21:34","source_url":"https://layerzeroscan.com/address/0x23c60095553F0D6ec2AB58631b4724D151d45309","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1440195207261065369","source_kind":"oft_address","curator_liquidity":false}
same_address+3{"chain":"base"}
peer_map+5{"via":{"address":"0x23c60095553f0d6ec2ab58631b4724d151d45309","chainSlug":"binance"},"adapter":"layerzero","oftAdapter":"0x3cd28e1a27db90720ae24bdde637ebce51160dee","unwrappedTo":"0x23c60095553f0d6ec2ab58631b4724d151d45309"}
binance canonical via layerzero
4
0x23c60095553f0d6ec2ab58631b4724d151d45309same open
illiquidpools hold $0, under the floor

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

discord+1{"notes":[],"proven":false,"ticker":"MMM","source_tx":null,"message_id":"1440195207261065369","message_ts":"2025-11-18T04:21:34","source_url":"https://layerzeroscan.com/address/0x23c60095553F0D6ec2AB58631b4724D151d45309","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1440195207261065369","source_kind":"oft_address","curator_liquidity":false}
registry+3{"tx":"0x3379347ebdf6ad6c41df35cf224872f66d7fcefa31722feae30182b362de64f0","from":"bridge_pin"}

How it moves between chains

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.

from base 1 of 1 reachable
binance layerzero 0x25fcc46a… 24 h ago
from binance 1 of 1 reachable
base layerzero 0x3379347e… 24 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9418 24 h ago layerzerobinance → base 0x3379347e…de64f0 DISCOVERED 53 min

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.

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.