4,015,372 launches on record
Coverage from 2 Sep 2026
Archive read 07:44 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-22 02:36 UTC

MASCOIN

Mascoin

9GQhJ7t7Gy8DyeMVxjJZuTsHvmoZro5sVDxzNxsFpump Solscan pump.fun

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

0.0%of supply taken by the creator in the first block
347outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 0.0%, 347 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 57% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

At launch

Created2026-11-22 02:36 UTC
CreatorGwGQgpBggD9h7Rqb1D7yxr26Ypc4w2yyqQejDcrJZVV3
Creator took0.0% of supply in the first block
Outside buyers347 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 45 within the first 30s, 3 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated39 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from3Y6mRutMf1iX95ftwYd1B5… slot 472,375,834
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-11-22 02:36:57 UTC
Slot 472,375,834, which is the chain's own clock for this moment.
Creation block3 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in45 distinct buyers, within the first thirty seconds.
A snapshot taken off a tick at the thirty-second mark, so it carries no moment of its own; it is placed here because that is where it happened.
Curve completed2026-11-22 03:15:55 UTC +38m 58s
Confirmed: a PumpSwap pool was found for it.

Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.

Seen before

This pictureOn 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 57% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 8 launches from 8 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.9% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 33.6% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 1 other creator wallet, across 3 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group of 2 creator wallets in all. Across the archive, 63.3% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity41.0 SOL
Read from chain2026-11-22 12:09 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameMascoin
DescriptionChristmas Runner
Metadata heldsha256 04b0b4fc3b13dffcbd5e87d61942c36b0bca82330de872ef0276b9c0cb83ba0c · 298 bytes
Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree.
Picture heldsha256 4e468a8914ecff48de2924fd61f0c7379df6024cde155bd039e59724ce843584 · 550,752 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-22 02:36 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another