1,017,257 launches on record
Coverage from 2 Sep 2026
Archive read 19:04 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

SCUM

No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

5HeDEbD2vfPpiHqw9m2RHfNCzdhvaZeDfMAd6PEjqBRo Solscan pump.fun
noteThe creator sold while we were watching.
noteOnly 4.6 SOL of liquidity was in the pool just now.

At launch

Created2026-09-27 17:52 UTC
CreatorFTuqW6J148wdknkPvm2EVSJ1EFt4aDhjAYzv6rdjuCRi
Creator took15.3% of supply in the first block
Outside buyers479 distinct wallets, not counting the creator, bought on the bonding curve: 187 within the first 30s, 1 bundled into the creation block.
Graduated2 min after launch
Curve, read on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldyes
Recorded from4rJAYrKzEgjouLCAm412pV… slot 451,069,548
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-27 17:52:57 UTC
Slot 451,069,548, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in187 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-09-27 17:54:36 UTC +1m 39s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-27 17:54:36 UTC +1m 39s
4.109e-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 21 launches from 20 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 79 launches from 62 creator wallets, including this one. See them →
This creator565 earlier launches, 27 confirmed graduated on chain, 5 with findings on record. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 347 other creator wallets, across 474 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets →

Pool

Liquidity4.6 SOL
Read from chain2026-09-28 21:15 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameNewsom
DescriptionFees to @gavinnewsom via UsePaid
Metadata heldsha256 ca7dd8f5a2be48f6d0868889d6ebe3aab45a533b9689ca5a3b09fddbe0a30cd2 · 453 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-09-28 17:53 UTC.
Picture heldsha256 6711fa5ae7d55c729374b875256d6ffd3c4396bba87d55db8f2b011978da67fe · 9,638 bytes

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