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

AST

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

AnacEELogzayHucD1tmPvz2Vqgy1qKZ5wbG2tT7Kpump Solscan pump.fun
findingOnly 3 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 47s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-10-01 03:58 UTC
Creator3NsTAKARF3HqgFj6JnnPU8iymmXfCfNcKrN9Z9rUJxak
Creator took0.2% of supply in the first block
Outside buyers3 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 0 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 13.8 h ago and it was finished. Checked 2026-10-01 08:01 UTC.
Creator soldyes
Recorded from379vkHkZPjdtM2KLMy8wUT… slot 452,173,065
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-01 03:58:51 UTC
Slot 452,173,065, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in1 distinct buyer, 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 03:59:38 UTC +47s
Confirmed against the venue's own completion state.
Highest price seen2026-10-01 03:59:43 UTC +52s
3.170e-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 31 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 55 launches from 16 creator wallets, including this one. See them →
This creator50 earlier launches, 3 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 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
NameAlset
Metadata heldsha256 e1b8e2965a4851f91dbba8efd2c6560b5842ca2124fba1d531400938a2022949 · 354 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 62942ef865c11b1ae59987dc053f2dd92238e124ac8c3c40cb092d1f1c4a8163 · 233,279 bytes

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