3,490,400 launches on record
Coverage from 2 Sep 2026
Archive read 16:55 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-11 05:08 UTC

LMAO

DAPKfEmjQRgX7NqgV6jS1rNLW65dgSdC1T181PJxpump Solscan pump.fun
0.3%of supply taken by the creator in the first block
20outside wallets bought on the bonding curve
Noreached a graduation threshold while we watched
6,384launches carry this ticker, from 1,628 creator wallets
4,487other launches declared this same launch document, byte for byte
5,753other launches used this exact picture file
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 5,753 other launches from 1,365 creator wallets in all, and this creator has 2,992 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.

noteThe creator sold while we were watching.

At launch

Created2026-11-11 05:08 UTC
Creator6c1Dmi9L4rTXT5GcTbTv8p3BuBEn8SJbo37UGJ3f6yfj
Creator took0.3% of supply in the first block
Outside buyers20 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: 15 within the first 30s, 0 in the very same block the token was created in.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldyes
Recorded from35zGhXRWxFwKiRtrQZReKa… slot 468,000,514
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-11 05:08:58 UTC
Slot 468,000,514, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Highest price seen2026-11-11 05:09:02 UTC +3s
2.814e-8 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 in15 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 5,740 launches from 1,365 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,384 launches from 1,628 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 4,487 other launches, across 1,278 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 creator2,992 earlier launches, 2 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
NameLMAO
Metadata heldsha256 72a9ece2987b5ae5bd274ad900592cbac7f949cd9ae28a4191715d3b232befcf · 173 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 1f94e196a2d396acb6747322e384f93a68c77c699e456f4521edebb37f1cdd68 · 35,755 bytes

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