STILL
The curve completed 4s 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 4s after launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 09:10 UTC |
| Creator | 2PfumWDPrZ4j4Pp6GFNNa7ERMkyUrC9rjx8P5jnxA4mq |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 30 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 0 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 | yes |
| Recorded from | 1Pc2RGzN3FYKBEQgxQ1bmk… slot 451,920,172
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 09:10:24 UTC Slot 451,920,172, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-30 09:10:29 UTC +4s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 09:10:29 UTC +4s
1.085e-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 | 1 distinct buyer, 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 5 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 74 launches from 61 creator wallets, including this one. See them → |
| This document | Byte-identical to 3 other launches' metadata document. See them → |
| This creator | 46 earlier launches, 3 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 17:48 UTC, just now |
What this launch claimed to be
| Name | STILL 2007 |
| Description | Log out. Put the phone down. It’s still 2007 outside. No AI. No doomscrolling. No 999+ notifications. Just friends, games and touching grass. $STILL |
| Metadata held | sha256 97ae171cae22405b784d4a799b91c2edabb066a5050849f0005c8751681cb872 · 343 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-10-01 09:11 UTC. |
| Picture held | sha256 0e38e90a7510a0dab43a97dce28277464badcc151ad5c2556e4bf634c35b230b · 365,489 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 09:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.