SR
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 5 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 3.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 15:54 UTC |
| Creator | Asw7LZsaZr97wxbqFz2SkDausDawRwHdrPAR2bNqknES |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 5 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 4.1 h ago and it was finished. Checked 2026-10-02 16:01 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3jzbNd7LscPZj7PR8Q3kMi… slot 452,656,478
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 15:54:14 UTC Slot 452,656,478, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 15:54:14 UTC +0s Confirmed against the venue's own completion state. |
| 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. |
| Highest price seen | 2026-10-02 16:03:20 UTC +9m 06s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 57 launches from 51 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.9 SOL |
| Read from chain | 2026-10-02 20:07 UTC, just now |
What this launch claimed to be
| Name | Super Retard |
| Description | Meet the silver lining on the dark side of the timeline. Every plan goes sideways. Somehow, that's the plan. |
| Metadata held | sha256 5941d70675261c75f0b0f50f474c74350ea656484ff65c4e85f3f7b7a50a080b · 426 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 ab8f8c9c86de7e10cb9cb334df7934d14383decfde3397f3b5833031c7fbe09c · 172,909 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 15:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.