Lone
The curve completed 15s 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 15s after launch.
noteThe creator sold while we were watching.
noteOnly 1.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-25 15:37 UTC |
| Creator | 232oN4sAg4j7zsAyGvozF9r5vaLWtxrjPwfBpB9eDRXo |
| Creator took | 0.3% of supply in the first block |
| Outside buyers | 26 distinct wallets, not counting the creator, bought on the bonding curve: 14 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 | 2CT2jGaAsdRwhao8jwEgSN… slot 450,395,082
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-25 15:37:38 UTC Slot 450,395,082, 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-25 15:37:53 UTC +15s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-25 15:37:53 UTC +15s
1.222e-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 | 14 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 214 launches from 100 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 219 launches from 104 creator wallets, including this one. See them → |
| This document | Byte-identical to 191 other launches' metadata document. See them → |
| This creator | 1,249 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 11 other creator wallets, across 7 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 | 1.0 SOL |
| Read from chain | 2026-09-25 19:04 UTC, just now |
What this launch claimed to be
| Name | Loneliness |
| Metadata held | sha256 35faec4a6d7ee900faaedb90cbeaf814a530eb0b64736280b3f5ce0a05326354 · 193 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 98ae202bf9f8df051316c9bc6e4a78946e3ea57745f756fc6a0014cb2001eff2 · 9,076 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-25 15:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.