3,742,437 launches on record
Coverage from 2 Sep 2026
Archive read 16 Nov 2026
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-16 13:56 UTC

USMS

FnTXZ2etkqj2g3iGpbMKzqxNytkg7RdUi2dzLdWupump 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.3%of supply taken by the creator in the first block
20outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 42s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 5,283 other launches from 1,294 creator wallets in all, and this creator has 80 other launches on record. 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, 56.6% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

findingIt left the curve 42s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-11-16 13:56 UTC
CreatorE9yzhH8UTPva2rCuhzsVdh4rs9XWRA8PJUW9d7FbcYNC
Creator took0.3% of supply in the first block
Outside buyers20 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: 5 within the first 30s, 0 in the very same block the token was created in.
Graduated1 min after launch
Curve on chainComplete. We read the bonding curve account 12.3 h ago and it was finished. Checked 2026-11-16 14:02 UTC.
Creator soldyes
Recorded from4vAg6Zn8YYNMgEtRc5Vx9m… slot 470,156,066
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-16 13:56:08 UTC
Slot 470,156,066, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in5 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-16 13:56:50 UTC +42s
Confirmed against the venue's own completion state.

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 5,272 launches from 1,294 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.6% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 5,093 launches from 1,331 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.7% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 4,132 other launches, across 1,227 creator wallets in all. Across the archive, 33.5% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator78 earlier launches. 18 reached the graduation threshold on our feed; we have read the curve account for 17, and 17 had not completed. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NameUSMS
Metadata heldsha256 6068888f0432ece926fc5ad8cd99bdc619b44b02aba1010244bbf05cfd4d35e8 · 122 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 df00c7fdbdfaa65e91366f12c4ede25ada5e6dae44b0e29a1bb56420d70dac60 · 49,211 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-16 13:56 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