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

SPEED

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.

Ey5w4dPtAFeJX147eL85UCSt47q56rxzihaptYfMpump 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-29 20:48 UTC
Creator91Awaaj6NCPpZ6oRmiiik6KfE7tWizCDZWQiPAitCFAo
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 chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot while we watched
Recorded from5gAkYUavCrbypSTjJHsoag… slot 451,753,694
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-29 20:48:19 UTC
Slot 451,753,694, 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-29 20:48:19 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: a PumpSwap pool was found for it.

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 12 launches from 12 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 249 launches from 168 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 4 other creator wallets, across 3 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

Liquidity0.3 SOL
Read from chain2026-10-01 06:07 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameSPEED GANG
DescriptionSPEED GANG (SPEED)
Metadata heldsha256 0cb705b1b99a697bcb08f3340cf715a73346542f08b5441173c66ef44e0ddbc5 · 343 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-30 20:48 UTC.
Picture heldsha256 ab8c3b8d135e969a0a9422f0af13febe11f70a6915e2390b3d3825352ceec59f · 386,029 bytes

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