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

KFC

The creator took 79% of supply at 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.

6tv7HG8MFgw4XEj88p8zYnNpGwocHWUTQn5hC9Bkpump Solscan pump.fun
findingThe creator bought its own bonding curve - 85 SOL, from the same wallet that created the token.
findingThe creator took 79.3% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
noteTook 1 bonding curve outright. 85 SOL spent on curves. We hold no market trades for it in either direction, so what it did with the tokens afterwards is not on our record.

At launch

Created2026-09-20 19:15 UTC
CreatorDMmSrYq1o1EVidx2pAaMMVSBCFQRXhmwgGLjq7NWTaU
Creator took79.3% of supply in the first block
Outside buyers0 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 0 bundled into the creation block.
Graduatedyes; we did not record when
Curve, read on chainComplete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-20 19:40 UTC.
Creator soldnot while we watched
Recorded from2f4EoXjTYng4U4ZTzc4bpK… slot 448,823,208
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-20 19:15:54 UTC
Slot 448,823,208, 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-20 19:15:54 UTC
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.
Thirty seconds inNo 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 completedRecorded as complete; we did not record when.
Confirmed against the venue's own completion state.

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 10 launches from 10 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 131 launches from 105 creator wallets, including this one. See them →
This documentByte-identical to 4 other launches' metadata document. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 4 other creator wallets, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 5 creator wallets. See the linked wallets →

Who took the curve

One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →

That is the same transaction the token was created in: the launch and the purchase of its float are one signature.

Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.

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
NameKFC
Descriptionhot ranch big dip has entered the chat
Metadata heldsha256 00a0180a4b1fef54d89908da085a76064c7161604ded3332960af7ce509cad41 · 387 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-21 19:17 UTC.
Picture heldsha256 72a81e543dce2e88ca3e652e9f4fec55222243b9a02b4acf28081ed34ee4f008 · 25,920 bytes

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