3,708,323 launches on record
Coverage from 2 Sep 2026
Archive read 06:29 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-17 21:14 UTC

GIB

Grok in Blender

3gHwCMKmRFJB49PhGaYXWP96LRQuk5hZXsC8hd7rpump 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

5.0%of supply taken by the creator in the first block
120outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
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 1 other launch from 2 creator wallets in all, and this creator has 2 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.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.

noteThe creator sold while we were watching.
noteOnly 1.5 SOL of liquidity was in the pool just now.

At launch

Created2026-09-17 21:14 UTC
Creator8C8GDou5aooFTWCZN5PAQBv7PFLsuyfeBrpmbtnikVvZ
Creator took5.0% of supply in the first block
Outside buyers120 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: 1 within the first 30s, 1 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.
Graduated10 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 soldyes
Recorded from2FCPyLHFHDtGC6jWEQbfZB… slot 447,894,723
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-17 21:14:39 UTC
Slot 447,894,723, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in1 distinct 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 completed2026-09-17 21:24:30 UTC +9m 51s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-17 21:45:50 UTC +31m 11s
7.687e-7 SOL per token. Decoded from an on-chain transaction that executed at that price. 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 2 launches from 2 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 59 launches from 50 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 1 other launch, across 2 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 creator2 earlier launches, none of which reached a graduation threshold while we watched. 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 5 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, 63.6% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity1.5 SOL
Read from chain2026-11-16 08:08 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameGrok in Blender
DescriptionHe built a model that can open an Ai, build almost any 3D object you describe, inspect the image it produced, notice it is wrong, and correct it without you touching the viewport
Metadata heldsha256 cd52c49ceee4ef506bfe0a32cae1cb4a444c2fbfcbfdf8dcfca5b6ba9931348a · 374 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-24 21:15 UTC.
Picture heldsha256 23b8225249aed0b46a0921b496d419235dcece8999f92b3a393564e0558af7d0 · 48,961 bytes

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