SM
The curve completed 45s 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.
findingIt left the curve 45s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 20:34 UTC |
| Creator | G2prUPkBAbSfJzmrfJ1PrQdxjNEwMvqfj1MrdWTkxrTQ |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 35 distinct wallets, not counting the creator, bought on the bonding curve: 5 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 | EBVzwBCrHJd97e5JzFBgnK… slot 452,073,538
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 20:34:56 UTC Slot 452,073,538, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 5 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-09-30 20:35:41 UTC +45s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 20:35:41 UTC +45s
1.396e-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. |
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 2 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 110 launches from 91 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 00:42 UTC, just now |
What this launch claimed to be
| Name | SUPER ME |
| Description | this 15$ all I have left let’s go to 100M ✅✅ |
| Metadata held | sha256 c15d2639fe63f359eb78eccfa451a99b0bd44a135c2a4f9853472b07049de3a1 · 238 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 bc00c0095da44a099a3484a7331b00cab3d7e3197e78dbc337339e0e862c934c · 83,493 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 20:34 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.