3,512,557 launches on record
Coverage from 2 Sep 2026
Archive read 06:31 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-09-02 20:00 UTC

pandatoken

panda

FX4xkQhQwMH4X8juNh6x2AZwUozorePCfh8HDGq7pump Solscan pump.fun
0.2%of supply taken by the creator in the first block
32outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
1other launch used this exact picture file
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all, and this creator has 34 other launches on record. 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. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. 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.

not establishedOur feed recorded this curve reaching the graduation threshold, but when we read the curve account on 2026-09-12 it was not complete. We do not state that this curve graduated.
noteThe creator sold while we were watching.

At launch

Created2026-09-02 20:00 UTC
CreatorG49BRDbbtWnqwCyWhv65JrWtmK7XbR6oaRCQWbReY7hq
Creator took0.2% of supply in the first block
Outside buyers32 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: 9 within the first 30s, 0 in the very same block the token was created in.
Graduated0 min after launch
Curve on chainIncomplete. We read the bonding curve account 61.5 days ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-09-12 00:12 UTC.
Creator soldyes
Recorded fromSMW6hDwphLQ5GUh2kwavfU… slot 443,782,876
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-02 20:00:43 UTC
Slot 443,782,876, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Highest price seen2026-09-02 20:00:43 UTC
3.694e-7 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.
Curve completed2026-09-02 20:01:06 UTC +23s
Not confirmed. An inference from decoded trade volume that nobody ever confirmed, and where the curve account has since been read, the great majority of those returned incomplete.
Thirty seconds in9 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.

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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This creator34 earlier launches. 5 reached the graduation threshold on our feed; we have read the curve account for 4, and 4 had not completed. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches →

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
Namepanda
Metadata heldsha256 52ba331d82995477ebdd78bae31fb0bad2f77568aeb705ce98facc7e8c350b1e · 366 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 a20a6a09905e67ae1ccfb69528787385a17cfd5c9a61c6210a23dd2fec040b29 · 277,394 bytes

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