3,699,765 launches on record
Coverage from 2 Sep 2026
Archive read 15 Nov 2026
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-15 11:27 UTC

PEARL

Tom Pearl

gupczrr4u7wkyCQq9xTm4Rfc14NYxuCMpX4Rfpapump 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 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. 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

12.5%of supply taken by the creator in the first block
593outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 12.5%, 593 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 7 other launches from 6 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.

At launch

Created2026-11-15 11:27 UTC
CreatorCR9csgh1fP5t2sNu3bJ89kg5QVhyJEQhFKdupo2EcCcg
Creator took12.5% of supply in the first block
Outside buyers593 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, 7 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.
Graduated7.3 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 from24rZsywfqJeM1xn2JowAJd… slot 469,712,594
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-15 11:27:38 UTC
Slot 469,712,594, which is the chain's own clock for this moment.
Creation block7 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
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.
Curve completed2026-11-15 18:42:42 UTC +7h 15m 04s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-11-15 19:11:20 UTC +7h 43m 42s
4.511e-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 8 launches from 6 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 259 launches from 247 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.7% 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, all of them this same creator's. Across the archive, 12.2% of the launches whose document we hold carry one only their own creator reused. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 5 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.6% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity62.2 SOL
Read from chain2026-11-16 03:12 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameTom Pearl
DescriptionLaunched on discord.gg/uxento
Metadata heldsha256 ce2895ffb94318b1e05f1159f7eb907453eb098b663628c2a47cb63a7af229ae · 343 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 e58f78ff0ec2297be4743bf476e266700287f78f8b44f2577c892920d7dce491 · 13,130 bytes

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