3,633,462 launches on record
Coverage from 2 Sep 2026
Archive read 13:17 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-09-02 13:01 UTC

RST

UK7TRR5F46PbuiycZNUYNZJgs6n1km9TKktcjqFpump 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

79.3%of supply taken by the creator in the first block
0outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The creator took 79% of supply at 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 38 other launches from 36 creator wallets in all, and this creator has 1 other launch 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.5% 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.

findingThe creator took 79.3% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.

At launch

Created2026-09-02 13:01 UTC
CreatorCjd1p3aiyoCyLHdGGQhFwhbqvPhvS2hgxLwtR7eSakXS
Creator took79.3% of supply in the first block
Outside buyers0 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: 0 within the first 30s, 0 in the very same block the token was created in.
Graduatedyes; we did not record when
Curve on chainComplete. We read the bonding curve account 65.8 days ago and it was finished. Checked 2026-09-09 23:04 UTC.
Creator soldnot while we watched
Recorded fromNot recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked.

Order of events

Created2026-09-02 13:01:30 UTC
Creation blockNo wallet bought in the block the token was created in.
Highest price seen2026-09-02 13:01:30 UTC
4.109e-7 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.
Thirty seconds inNo buyer, 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 completedRecorded as complete; we did not record when.
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 39 launches from 36 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 177 launches from 140 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.6% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 6 other launches, across 6 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator1 earlier launch, 1 confirmed complete on chain, 1 with findings on record. 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
NameRST
DescriptionRST (RST)
Metadata heldsha256 58f2dd90042266f35e4c269666df235b0b047fd9c5bbf80ad2eb3a2589798677 · 341 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-23 01:10 UTC.
Picture heldsha256 9b9d962f29b6b1510fed404e142660b845934d6b278c3ed3d8878b3cbf9ea198 · 252,652 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 20:18 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