SP
The curve completed in the same batch of events as the 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.
findingOnly 6 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 2.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 14:15 UTC |
| Creator | 3hT37BmHnF7eKgmDts74KsHQpboTrmug6MtHjvPtVgWs |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 6 distinct wallets, not counting the creator, bought on the bonding curve: 6 within the first 30s, 6 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 | 2Rq2DAPKeZrH22eEPTmGXa… slot 451,665,852
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 14:15:28 UTC Slot 451,665,852, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 14:15:28 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 14:15:28 UTC +0s
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 | 6 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 3 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 184 launches from 147 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, 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 → |
Pool
| Liquidity | 2.7 SOL |
| Read from chain | 2026-09-30 21:43 UTC, just now |
What this launch claimed to be
| Name | Super Pepe |
| Description | the city had no hero. so a frog put on a cape. $SP on sol |
| Metadata held | sha256 1a04eb1df1c4057a65084d82f52293385294e5e075906817b993843798316a75 · 397 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-read | Byte-identical to the launch-time capture when re-read 2026-09-30 14:16 UTC. |
| Picture held | sha256 1e89cac275049f2d4bf170a6def80392d3993b9918233b469fa8f2a533afdcf4 · 127,944 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 14:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.