PUMPCHAN
The creator took 26% 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.
noteThe creator took 26.5% of supply at launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 02:14 UTC |
| Creator | 4erQUfuoyF7wLVeBHd6mMxbicy196gUbUqw3oqQyoLUm |
| Creator took | 26.5% of supply in the first block |
| Outside buyers | 384 distinct wallets, not counting the creator, bought on the bonding curve: 214 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Not 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 sold | not while we watched |
| Recorded from | 55W1ZWi9t86cqQoHLAYVo5… slot 452,149,689
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 02:14:49 UTC Slot 452,149,689, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-10-01 02:14:49 UTC
0.000e+0 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 in | 214 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. |
| Curve completed | 2026-10-01 02:16:15 UTC +1m 26s 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 picture | On 13 launches from 12 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 99 launches from 72 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 07:37 UTC, just now |
What this launch claimed to be
| Name | Pumpchan |
| Metadata held | sha256 5e40bba8e50fc0629e0e10a1666d3a279562718a2091ef906a32cc7a19491061 · 454 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 held | sha256 6f25d15668f6c54483a4cc30cc3e208747ff4d10e926b065b93b02c994c3f40b · 4,814 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 02:14 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.