644,547 launches on record
Coverage from 2 Sep 2026
Archive read 22 Sep 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

SLJ

The curve completed 19s 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.

3XYdRZ1Y2iEaXspZqiWb4LxQwy1F9bMZPER7QStxpump Solscan pump.fun
findingIt left the curve 19s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-22 13:04 UTC
Creator5jRjK8pqQPneT1DAqNPgpQreE2mWh8NHRe6gCiwFVt4v
Creator took0.9% of supply in the first block
Outside buyers39 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 0 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 5.7 h ago and it was finished. Checked 2026-09-22 18:46 UTC.
Creator soldyes
Recorded fromY3iuDJ2CHVzCdsvmtztUop… slot 449,386,943
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-22 13:04:02 UTC
Slot 449,386,943, 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-22 13:04:21 UTC +19s
Confirmed against the venue's own completion state.
Thirty seconds in7 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-22 13:06:48 UTC +2m 45s
8.942e-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 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 8 launches from 1 creator wallet, including this one. See them →
This documentByte-identical to 7 other launches' metadata document. See them →
This creator424 earlier launches, 0 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 28 other creator wallets, across 19 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

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
NameSLJ PUMP
DescriptionSLJ PUMP
Metadata heldsha256 e00964c6abbdeb3f1d6ba967640646e5510fdb11447af69e1ba0481760c5ada3 · 197 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 fa3e30c9b81eb35066a4d7059c68143a13063cff0c1c46c34683a87a534363d6 · 339,058 bytes

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