3,525,300 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 10:11 UTC

Parrot

Party Parrot

3Yoj6vQYTHfFVVBwHGNDbxBhh6R7iw41BSrNSGJ4pump Solscan pump.fun
15.0%of supply taken by the creator in the first block
1,035outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
149launches carry this ticker, from 128 creator wallets
3other launches declared this same launch document, byte for byte
14other launches used this exact picture file
Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 15.0%, 1,035 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this picture is on 14 other launches from 11 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.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.

At launch

Created2026-11-12 10:11 UTC
CreatorB9KtuhgEwnY5JASR5W8Yjq5t3Xw1uzr6Uz55mjaGeLCd
Creator took15.0% of supply in the first block
Outside buyers1,035 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: 52 within the first 30s, 0 in the very same block the token was created in.
Graduated1.1 h 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 from4e6CxcncqxsKaZHf2vTz8m… slot 468,486,967
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-12 10:11:10 UTC
Slot 468,486,967, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in52 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-12 11:15:40 UTC +1h 04m 30s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-11-12 12:05:27 UTC +1h 54m 17s
6.178e-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 15 launches from 11 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 149 launches from 128 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 3 other launches, across 3 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 →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 2 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.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity47.9 SOL
Read from chain2026-11-12 17:03 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameParty Parrot
Metadata heldsha256 f4787ff4f82c989583cf277cf91c1a640cd2ad8371d4beccec5abe7d6801b82e · 369 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 ae359da5188e228720408fb8c6bc53486d888a9d8be51ebc343284a71f038b40 · 631,940 bytes

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