3,643,462 launches on record
Coverage from 2 Sep 2026
Archive read 20:13 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-14 18:49 UTC

#dat

znuT9EVmyNmBS3Fwg1SKcRYDvtw5QT7ZAdFha2Mpump Solscan pump.fun

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

6.6%of supply taken by the creator in the first block
348outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

Also recorded, and not part of the finding above: this picture is on 4 other launches. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. They are listed under Seen before, further down this page.

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

noteOnly 2.8 SOL of liquidity was in the pool just now.

At launch

Created2026-11-14 18:49 UTC
Creator3LeskwcskZXfBZmqr4GETLzhsiXDYix7iWaZracQDm2h
Creator took6.6% of supply in the first block
Outside buyers348 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 110 within the first 30s, 9 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated3 min after launch
Curve on chainComplete. We read the bonding curve account 2.8 h ago and it was finished. Checked 2026-11-14 19:01 UTC.
Creator soldnot while we watched
Recorded from643nqJgToNCRJVjZuHZpfT… slot 469,434,206
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-14 18:49:40 UTC
Slot 469,434,206, which is the chain's own clock for this moment.
Creation block9 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in110 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-11-14 18:52:28 UTC +2m 48s
Confirmed against the venue's own completion state.
Highest price seen2026-11-14 18:52:28 UTC +2m 48s
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.

Pool

Liquidity2.8 SOL
Read from chain2026-11-14 21:52 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Name#dat
Descriptiondeployed on https://track.tech/
Metadata heldsha256 6781de04e7548ba2fd716225efff12bf82785bbe794607e6ffd03a80df30dc62 · 280 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 08ab9abee7c2cc536c36cc9a9318d2450a0a7f8dc7a6f8ff8f2af0650d60196e · 2,533 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-14 18:49 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