PUMP
The curve completed 3s after 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 30.4% of supply at launch.
findingIt left the curve 3s after launch.
noteOnly 9.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-22 16:37 UTC |
| Creator | 27BBTD7xKf6hLV6RuEMv76Qww8AvCGnC5J6SaGmaeY1S |
| Creator took | 30.4% of supply in the first block |
| Outside buyers | 55 distinct wallets, not counting the creator, bought on the bonding curve: 55 within the first 30s, 2 bundled into the creation block. |
| Graduated | 0 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 | 3AJ6mW9uTGYZ1PzrAvSkLq… slot 449,434,861
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-22 16:37:53 UTC Slot 449,434,861, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-22 16:37:55 UTC +3s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-22 16:37:55 UTC +3s
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 in | 55 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. |
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 12 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 1,552 launches from 647 creator wallets, including this one. See them → |
Pool
| Liquidity | 9.9 SOL |
| Read from chain | 2026-09-23 00:32 UTC, just now |
What this launch claimed to be
| Name | PUMP |
| Metadata held | sha256 2265af4a107e205f25fd0c4349a701467c7ba94a3596b00ad49d697343922bc7 · 311 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 0bad852abb0edd0047d832e105d5ef54a3e4ee9cc15e9bd5231fd3039daee9c3 · 5,654 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 16:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.