3,615,454 launches on record
Coverage from 2 Sep 2026
Archive read 06:28 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-14 03:02 UTC

Believe

AsT342xoepuoPHByTDT2cocJWuH342sNzy4Xegifpump 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 five lists, or with Brand Protection at $79 a month for every list on every record. 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

3.4%of supply taken by the creator in the first block
62outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 7s after 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 7 other launches from 4 creator wallets in all. 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.

findingIt left the curve 7s after launch.

At launch

Created2026-11-14 03:02 UTC
Creator6i7qtTanXzrWQNdjHSkhMN8DaY1tq3kZ8VMFQpNPzJgn
Creator took3.4% of supply in the first block
Outside buyers62 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: 62 within the first 30s, 15 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 4.0 h ago and it was finished. Checked 2026-11-14 03:31 UTC.
Creator soldnot while we watched
Recorded fromcg2U5V4cc3g8NHCvo7AAx3… slot 469,170,110
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-14 03:02:56 UTC
Slot 469,170,110, which is the chain's own clock for this moment.
Creation block15 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-14 03:03:03 UTC +7s
Confirmed against the venue's own completion state.
Thirty seconds in62 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 4 launches from 4 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 441 launches from 360 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 2 other launches. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

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
NameBelieve
Metadata heldsha256 6ce0937030f3b6945fe0df5c3a50a4ad97b82e1b68cecf0a89ef9388faa6c2c8 · 282 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 b74048a9f29334f8730413a63632d9c807bdc1be74da20a86e7669d0bca1b0f0 · 226,857 bytes

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