3,474,570 launches on record
Coverage from 2 Sep 2026
Archive read 10:05 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-10-31 04:50 UTC

LMAO

6vjvXcVNHHqqgaV91Aac6SbdjsFWixQxpAY6NqRKpump Solscan pump.fun
74.4%of supply taken by the creator in the first block
1outside wallet bought on the bonding curve
Yesreached a graduation threshold while we watched
6,350launches carry this ticker, from 1,619 creator wallets
1,076other launches declared this same launch document, byte for byte
5,724other launches used this exact picture file
The creator took 74% 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 5,724 other launches from 1,358 creator wallets in all, and this creator has 636 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.

findingThe creator bought its own bonding curve - 68 SOL, from the same wallet that created the token.
findingThe creator took 74.4% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
findingThat purchase is what completed the curve: the token left the curve on the creator's own money.
findingOnly 1 outside buyer bought on the bonding curve before it graduated.
findingIt left the curve 7s after launch.
noteTook 6 bonding curves outright. 471 SOL spent on curves. We hold no market trades for it in either direction, so what it did with the tokens afterwards is not on our record.
noteOnly 9.2 SOL of liquidity was in the pool just now.

At launch

Created2026-10-31 04:50 UTC
CreatorCBF9xK2T7FhWk6wafZHujJUugbNJRND22b3foRZgxhbR
Creator took74.4% of supply in the first block
Outside buyers1 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, 0 in the very same block the token was created in.
Graduated0 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 soldnot while we watched
Recorded from3AcmkSggG4BojaczrYp9oz… slot 463,560,232
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-31 04:50:41 UTC
Slot 463,560,232, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-31 04:50:48 UTC +7s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-31 04:50:48 UTC +7s
4.184e-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.
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.

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 5,708 launches from 1,358 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 6,350 launches from 1,619 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 1,076 other launches, across 201 creator wallets in all. Across the archive, 33% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator636 earlier launches. 39 reached the graduation threshold on our feed; we have read the curve account for 37, and 37 had not completed, 27 with findings on record. 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 1 other creator wallet, across 3 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 of 2 creator wallets in all. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Who took the curve

One transaction bought 68 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →

That is the same transaction the token was created in: the launch and the purchase of its float are one signature.

Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.

Pool

Liquidity9.2 SOL
Read from chain2026-11-11 16:49 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameLMAO
Metadata heldsha256 c23c3d7d7812840e3cc74414e8076f3b74050c4091fd3d0f8d6b734b5ea17cf8 · 186 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-11-07 04:51 UTC.
Picture heldsha256 1f94e196a2d396acb6747322e384f93a68c77c699e456f4521edebb37f1cdd68 · 35,755 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-31 04:50 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