1,163,867 launches on record
Coverage from 2 Sep 2026
Archive read 12:02 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

lonshor

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

8ez5vbfy6NNa5wgbwi9VYNRAmsFAcDzg5vbU1eRMpump Solscan pump.fun
findingIt left the curve 41s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-10-01 02:58 UTC
CreatorCQLZTA839DygaeS5y7nYTUW5mJEVciRv5wbfhw8ecTch
Creator took3.4% of supply in the first block
Outside buyers150 distinct wallets, not counting the creator, bought on the bonding curve: 111 within the first 30s, 7 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 13.0 h ago and it was finished. Checked 2026-10-01 03:01 UTC.
Creator soldyes
Recorded from3cHAvHqTr7Ze6dvNVF8Xds… slot 452,159,375
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-01 02:58:02 UTC
Slot 452,159,375, 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 in111 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-10-01 02:58:43 UTC +41s
Confirmed against the venue's own completion state.
Highest price seen2026-10-01 02:58:43 UTC +41s
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 7 launches from 7 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 8 launches from 8 creator wallets, including this one. See them →
This documentByte-identical to 5 other launches' metadata document. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 6 other creator wallets, across 3 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
Namelonshor
Metadata heldsha256 75c1f8957a6651ae55d5dc3949e17ae2c95cc45a23ad90f328c7e569e9663695 · 262 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 ec0c72b6a0d4386ff7f2911a4ca60a63838b66abb13be073ce6e8a321c21e5d0 · 5,885 bytes

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