Token Dashboard
tokens
1963
contracts
6143
confirmed
5691 of 6143
chains seen
14
unmeasured
169
queued
0

MCLB

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

Lifecycle

  1. first pin received 2026-09-03 06:06:14 UTC · 2 d ago #6501 via layerzero
  2. token discovered 2026-09-03 08:14:19 UTC · 2 d ago 5 contracts today
  3. first liquid 2026-09-05 00:22:43 UTC · 1 min ago a chain quoted liquid
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

base mint burn via layerzero 10
0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579same open
illiquidno route found

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

same_address+3{"chain":"base"}
codehash+2{"codehash":"0xf0c497a104008802e0cafcca9e68c7432638de70d4f6042ca79cb71feb785718"}
peer_map+5{"via":{"address":"0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579","chainSlug":"sonic"},"adapter":"layerzero"}
binance mint burn via layerzero potential · no transfer seen 8
0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579same open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"binance"}
peer_map+5{"via":{"address":"0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579","chainSlug":"sonic"},"adapter":"layerzero"}
arbitrum mint burn via layerzero 8
0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579same open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"arbitrum"}
peer_map+5{"via":{"address":"0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579","chainSlug":"sonic"},"adapter":"layerzero"}
avalanche mint burn via layerzero 8
0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579same open
illiquidpools hold $0, under the floor

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

same_address+3{"chain":"avalanche"}
peer_map+5{"via":{"address":"0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579","chainSlug":"sonic"},"adapter":"layerzero"}
sonic canonical via layerzero 3
0x44e23b1f3f4511b3a7e81077fd9f2858df1b7579same open
liquid404 bps · 4.04% via kyberswap

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

registry+3{"tx":"0xe95d0eeba0040d15f23af5eb0969906dbcaf6208d0583b994e9d962e822eb8ad","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 0 of 4 reachable

No transfer has been seen leaving arbitrum.

show 4 unreachable hide unreachable
avalanche no transfer seen
base no transfer seen
binance no transfer seen
sonic no transfer seen
from avalanche 1 of 4 reachable
base layerzero 0xcc0e502f… 2 d ago
show 3 unreachable hide unreachable
arbitrum no transfer seen
binance no transfer seen
sonic no transfer seen
from base 1 of 4 reachable
arbitrum layerzero 0x49e93a46… 2 d ago
show 3 unreachable hide unreachable
avalanche no transfer seen
binance no transfer seen
sonic no transfer seen
from binance 0 of 4 reachable

No transfer has been seen leaving binance.

show 4 unreachable hide unreachable
arbitrum no transfer seen
avalanche no transfer seen
base no transfer seen
sonic no transfer seen
from sonic 1 of 4 reachable
base layerzero 0xe95d0eeb… 2 d ago
show 3 unreachable hide unreachable
arbitrum no transfer seen
avalanche no transfer seen
binance no transfer seen

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#6501 2 d ago layerzerosonic → base 0xe95d0eeb…2eb8ad DISCOVERED 2 h 8 min

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.