3,683,106 launches on record
Coverage from 2 Sep 2026
Archive read 16:48 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-15 15:49 UTC

Verafy

2q3dSGCiZQ7gb4eDqx9pwYoot48keWtAQdRha8jtpump 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.

Its own first blocks

27.8%of supply taken by the creator in the first block
332outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The creator took 28% 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 9 other launches from 8 creator wallets in all, and this creator has 11 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.

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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 took 27.8% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 6.4 SOL of liquidity was in the pool just now.

At launch

Created2026-11-15 15:49 UTC
CreatorGe9ekqsgMBqN1xeEYVMV2DbGk6aNwXCkfJX47cEM2PzF
Creator took27.8% of supply in the first block
Outside buyers332 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.
Graduated1 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 from5qBBw8vEys5q3mnaEKGBGJ… slot 469,785,689
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-15 15:49:24 UTC
Slot 469,785,689, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in224 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-15 15:50:42 UTC +1m 18s
Confirmed against the venue's own completion state.
Highest price seen2026-11-15 15:50:42 UTC +1m 18s
4.109e-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 10 launches from 8 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 24 launches from 19 creator wallets. 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 other launches, across 4 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 creator11 earlier launches, 1 confirmed complete on chain. Across the archive, 70.8% 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 25 other creator wallets, across 25 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.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity6.4 SOL
Read from chain2026-11-15 21:57 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameVerafy
DescriptionFees to @rexstjohn via UsePaid
Metadata heldsha256 c49061384e670c8734a822a4e30f2d4a154aed728578d95644c225290fa2c14b · 353 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 93ec318f64bc8c728422edfc466ac6fd9b0dd0b89d936ea94636bb47fa16ca54 · 3,518 bytes

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