530,561 launches on record
Coverage from 2 Sep 2026
Archive read 14:14 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

Pigeon

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.

DDKt1nPsy4nab8sMB5AWsHzUjbBTTGCFuvfFS3b3pump 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.
noteOnly 0.3 SOL of liquidity was in the pool just now.

At launch

Created2026-09-19 12:18 UTC
Creator4Fxa1P6PjMYy4ZZWQFYqUYHp197BWtHygpPKTdUj6pqZ
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 3.8 h ago and it was finished. Checked 2026-09-19 12:18 UTC.
Creator soldnot while we watched
Recorded from4rQmqinstWmBHcv45XmaHb… slot 448,405,320
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-19 12:18:06 UTC
Slot 448,405,320, 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-19 12:18:06 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 123 launches from 17 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 190 launches from 76 creator wallets, including this one. See them →
This documentByte-identical to 2 other launches' metadata document. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 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 →

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

Liquidity0.3 SOL
Read from chain2026-09-19 16:04 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameThe Depressed Pigeon
DescriptionFees to @numanuk via UsePaid
Metadata heldsha256 2bef18378c526e0fe81cb767ccc552b594001a572f2811d08ec00a095451c0dc · 461 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 800d0e8a8c4790189e1f25603f9c365282b392be9bd23be44e0b63a2bcf74bef · 7,280 bytes

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