1,153,255 launches on record
Coverage from 2 Sep 2026
Archive read 06:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

UP

The curve completed 18s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

Fm2cBSeHEUPDwHvv6Ccpi4mJ3vei9XvuP74c7d7ypump Solscan pump.fun
findingIt left the curve 18s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-29 16:01 UTC
Creator9xMyCJBrqawR82w3ReXnoEEFRvVx8Rdn7o3f4NhXcsr1
Creator took0.2% of supply in the first block
Outside buyers15 distinct wallets, not counting the creator, bought on the bonding curve: 8 within the first 30s, 0 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-29 23:32 UTC.
Creator soldyes
Recorded from4wfaSna3W3VCTTHUxnhRz2… slot 451,689,514
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-29 16:01:26 UTC
Slot 451,689,514, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-09-29 16:01:44 UTC +18s
Confirmed against the venue's own completion state.
Thirty seconds in8 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.
Highest price seen2026-09-29 16:02:33 UTC +1m 07s
1.827e-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 4 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 744 launches from 443 creator wallets, including this one. See them →
This creator20 earlier launches, 0 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 3 other creator wallets, across 7 shared artifacts, each matched by hash. Together they sit in a linked group of 5 creator wallets. See the linked wallets →

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
NameUPTOBER
DescriptionITS UPTOBER, BABY
Metadata heldsha256 44de6f6e20d2c059cdebf27230e0fc682812ab7e9c5b5b37295324634305fbd8 · 308 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-30 16:02 UTC.
Picture heldsha256 3f018c4daade9219d688f658c5725471bf0db74c4ca8fc1db28049de0b38e0be · 283,803 bytes

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