3,489,776 launches on record
Coverage from 2 Sep 2026
Archive read 16:55 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-03 00:02 UTC

ROCKSTAR

Rockstar Games

5XvcnJi25XgGDrvWyyJwKM2tWNQhSisGfaEsS3G8pump Solscan pump.fun
0.2%of supply taken by the creator in the first block
18outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
490launches carry this ticker, from 398 creator wallets
6other launches used this exact picture file
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 6 other launches from 6 creator wallets in all, and this creator has 91 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.2% 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.

not establishedOur feed recorded this curve reaching the graduation threshold, but when we read the curve account on 2026-09-12 it was not complete. We do not state that this curve graduated.

At launch

Created2026-09-03 00:02 UTC
Creator3c3uoWgKuhoShhq4XHeGuqhAy8WDXqUAf33QtJHbTiLT
Creator took0.2% of supply in the first block
Outside buyers18 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: 4 within the first 30s, 0 in the very same block the token was created in.
Graduated2 min after launch
Curve on chainIncomplete. We read the bonding curve account 60.9 days ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-09-12 00:12 UTC.
Creator soldnot while we watched
Recorded from3EAWAsrzUdVXtuZC1K7g1L… slot 443,828,919
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-03 00:02:24 UTC
Slot 443,828,919, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in4 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-09-03 00:04:01 UTC +1m 38s
Not confirmed. An inference from decoded trade volume that nobody ever confirmed, and where the curve account has since been read, the great majority of those returned incomplete.
Highest price seen2026-09-03 00:04:01 UTC +1m 38s
1.269e-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.

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 7 launches from 6 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 490 launches from 398 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.5% wear one that more than one creator wallet has launched. See this ticker's page →
This creator91 earlier launches, 2 confirmed complete on chain. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 4 other creator wallets, across 17 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 64% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

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
NameRockstar Games
DescriptionThe official coin of Rockstar Games on PUMP.FUN Watch Grand Theft Auto VI: An Extended Look. Now on @netflix: netflix.com/GTAVI
Metadata heldsha256 ffd92d0b95ec10ed974073755ac2c17628baafc32503bf68d3fa3bb5bfeb8e85 · 510 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 d77ad81614a26e48661ec19df9052f967ff9ede3952520b4ca3f88a51e7482c2 · 18,136 bytes

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