Read the create block
The block of the create transaction and the two after it, decoded from pump.fun's own trade events: every buy, every failed attempt, in block order.
Every launch opened at slot 0. See which buyers were linked to the creator, which weren't, and what every dev did before. Every link proven on chain.
Today· 2,287 launches· 84.9% clean· 7.0% linked slot-0 buys· updated 44s ago
Today counts from 05:09 UTC, when the indexer started.
Launches today
+614 last hour
Clean rate
7-day average after the first full day
Supply bought by linked wallets
avg in slot 0 per launch with linked buys · 160 launches
| period | launches | clean | linked buys | sniped |
|---|---|---|---|---|
| 2026-10-26 05:00–06:00 UTC | 1063 | 874 | 93 | 115 |
| 2026-10-26 06:00–07:00 UTC | 1049 | 910 | 61 | 79 |
| 2026-10-26 07:00–08:00 UTC | 175 | 157 | 6 | 16 |
UTC hours. The indexer started 2026-10-26 05:09 UTC; earlier hours have no data.
How it works
The block of the create transaction and the two after it, decoded from pump.fun's own trade events: every buy, every failed attempt, in block order.
SOL sent between each buyer and the creator, shared funders, and tokens passed back within 24 hours. Exchange hot wallets are never a link.
Clean, linked buys, sniped, dev-heavy or quiet, each with its reason and the transactions behind it, then the dev's record across every launch.
Live feed
One at a time, so it stays readable. Market cap is read one hour after launch.
| time | token | labels | slot 0 | linked | unlinked | dev initial | proofs |
|---|---|---|---|---|---|---|---|
| $CHIMPSHOT CHIMP | CLEANQUIET |
0% | 0% | 3.4% | proofs → | ||
| 10 SOL WOULD CHANGE MY LIFE SOL=DAD | CLEANQUIET |
0% | 0% | 0.2% | proofs → | ||
| Pumpkin Pumpkin | CLEANSNIPED |
0% | 22.4% | 0% | proofs → | ||
| The Addict ADDICT | CLEANQUIET |
no buys in slot 0 |
0% | 0% | 0% | proofs → | |
| American by blood 🇺🇸 elon | CLEANQUIET |
0% | 0% | 0.4% | proofs → | ||
| Viva La France 🔥 | CLEANQUIET |
0% | 0% | 0.3% | proofs → | ||
| The Addict ADDICT | CLEANSNIPED |
0% | 24.3% | 0% | proofs → | ||
| goku coin sol | CLEANQUIET |
0% | 0% | 3.4% | proofs → | ||
| Let it run Litr | CLEAN |
0% | 0.9% | 0.4% | proofs → | ||
| green cat GrenCAT | CLEANQUIET |
0% | 0% | 1.6% | proofs → | ||
| he just claimed! genny! Free Bots | CLEAN |
0% | 0.07% | 0% | proofs → | ||
| has nothing to do with jito… HSDT | CLEAN |
0% | 8.2% | 0.04% | proofs → | ||
| Undo It Undo | CLEANQUIET |
no buys in slot 0 |
0% | 0% | 0% | proofs → | |
| wrappedape wApe | CLEAN |
0% | 0.2% | 4.0% | proofs → | ||
| commotitties commotitties | CLEANQUIET |
no buys in slot 0 |
0% | 0% | 0% | proofs → | |
| dex goons dex | CLEANSNIPED |
0% | 22.6% | 0% | proofs → | ||
| 0n3xxxx $One | CLEANQUIET |
0% | 0% | 3.4% | proofs → | ||
| Baaiim monkey BAAIIM | CLEANQUIET |
0% | 0% | 0.3% | proofs → | ||
| PEPE2.0 PEPE2.0 | CLEANQUIET |
0% | 0% | 0.2% | proofs → | ||
| commotitties commotitties | DEV-HEAVYSNIPED |
0% | 16.2% | 6.6% | proofs → | ||
| TRUMP MAGA | CLEANQUIET |
0% | 0% | 0.2% | proofs → | ||
| MCP MCP | CLEANQUIET |
0% | 0% | 1.7% | proofs → | ||
| Undo It Undo | DEV-HEAVY |
0% | 8.0% | 22.9% | proofs → | ||
| Mental Health Awareness HEALTH | CLEANQUIET |
no buys in slot 0 |
0% | 0% | 0% | proofs → | |
| Megan Fox Fox | CLEANQUIET |
0% | 0% | 1.7% | proofs → | ||
| SOL PLEASE FOR ME SOL PLEASE | CLEANQUIET |
0% | 0% | 0.2% | proofs → | ||
| The Neurodivergent Bull Hexumlite | CLEANQUIET |
no buys in slot 0 |
0% | 0% | 0% | proofs → | |
| Holy Coin HOLYCOIN | CLEANQUIET |
0% | 0% | 0.4% | proofs → | ||
| Gamblineers GAMBLIE | DEV-HEAVYQUIET |
0% | 0% | 6.6% | proofs → | ||
| ELON RESPONDED TO AGENT V READ | CLEANQUIET |
no buys in slot 0 |
0% | 0% | 0% | proofs → |
At least 3 launches in 7 days, every one CLEAN, ranked by launches still trading after 24 h.
0 still trading after 24 h · 5 bought by others in slot 0
0 still trading after 24 h · 3 bought by others in slot 0
0 still trading after 24 h · 2 bought by others in slot 0
0 still trading after 24 h · 1 bought by others in slot 0
0 still trading after 24 h · 1 bought by others in slot 0
0 still trading after 24 h · 1 bought by others in slot 0
Share of supply bought in slot 0 by wallets linked to the creator or funded together.
6 slot-0 buyers in 2 same-funder groups bought 26.6% of supply in slot 0
6 slot-0 buyers in 2 same-funder groups bought 26.5% of supply in slot 0
5 slot-0 buyers in 2 same-funder groups bought 25.9% of supply in slot 0
5 slot-0 buyers in 2 same-funder groups bought 25.9% of supply in slot 0
5 wallets linked to the creator bought 23.5% of supply in slot 0
3 slot-0 buyers funded by the same wallet bought 23.0% of supply in slot 0
Builders
A remote MCP server with four read-only tools: check a launch, a dev's record, the day's numbers, recent launches. Or the REST API, 60 requests a minute, no key.
API & MCP docs →claude mcp add --transport http block-zero https://blockzero.site/mcp
The slot (about 400 ms of Solana) that holds the transaction creating the coin. Buys in the same slot happen before almost anyone could see the coin exist. Block Zero reads that block, and the two after it, for every pump.fun launch.
A concrete on-chain link between a buyer and the creator, shown with the transaction that proves it: SOL sent between them in the week before launch, funding from the same wallet that funded the creator (exchange wallets excluded), or tokens sent to the creator or a linked wallet within 24 hours.
Yes, within stated limits. Funding older than 7 days, trails through exchanges, and very busy wallets beyond the read cap are not seen; a partial record says what could not be read. The method and every limit are on the methodology page.
Every launch and dev page has a “Dispute this record” link. A person reads every dispute; a record found wrong is corrected or annotated, with the reason logged.
No. It is a record of what happened on chain: who bought in the first slot, how they were funded, and what they did in the first day.
Every pump.fun create since the indexer started, found from chain data (a WebSocket plus a gap-free reconciler), and older launches of any dev someone looks up. Measured coverage is published on the methodology page.