3,524,935 launches on record
Coverage from 2 Sep 2026
Archive read 13:18 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-12 09:24 UTC

PAID

Paid

BGTDMnCg9w4gv8nVzf7kfcdnP7RYuUHAEMawwRMgpump Solscan pump.fun
0.2%of supply taken by the creator in the first block
6outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
1,589launches carry this ticker, from 1,060 creator wallets
2other launches declared this same launch document, byte for byte
387other launches used this exact picture file
The curve completed in the same batch of events as the 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 387 other launches from 248 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.3% 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.

findingOnly 6 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.

At launch

Created2026-11-12 09:24 UTC
Creator2dpdWc1x28viNEpMYMA4T9nokcbTDZPbtZGBzah8mjyg
Creator took0.2% of supply in the first block
Outside buyers6 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: 6 within the first 30s, 6 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.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 6.6 h ago and it was finished. Checked 2026-11-12 09:30 UTC.
Creator soldnot while we watched
Recorded from35P3oG1jPhTAKf8beDyYJ1… slot 468,473,908
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-12 09:24:32 UTC
Slot 468,473,908, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-12 09:24:32 UTC +0s
Confirmed against the venue's own completion state.
Thirty seconds in6 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.

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 388 launches from 248 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 1,589 launches from 1,060 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 documentThe same launch document, byte for byte, as 2 other launches, across 2 creator wallets in all. Across the archive, 33.1% 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. 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
NamePaid
Metadata heldsha256 94e1d7ab44d848417dae5742eb8b56fa12490547aecb249d4b19a1a8c5285aca · 239 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 8a64053914758c43767dd78e665ecc430006b4d49aa9b7bb7aedc260330ea3ea · 9,462 bytes

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