POC
The curve completed 29s 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 29s after launch.
At launch
| Created | 2026-10-01 21:08 UTC |
| Creator | 4ouxnb7kHVYsBugmsKfhR2uiCjpRH6PbtS5r18Si5VJi |
| Creator took | 7.0% of supply in the first block |
| Outside buyers | 92 distinct wallets, not counting the creator, bought on the bonding curve: 92 within the first 30s, 13 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 | 4X91uCxSvyfQH4Zd1JhMNm… slot 452,403,908
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 21:08:31 UTC Slot 452,403,908, which is the chain's own clock for this moment. |
| Creation block | 13 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 21:09:00 UTC +29s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 92 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-01 23:56:41 UTC +2h 48m 10s
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 | On 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 32 launches from 29 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
Pool
| Liquidity | 64.1 SOL |
| Read from chain | 2026-10-02 02:30 UTC, just now |
What this launch claimed to be
| Name | POC |
| Description | put or calls? |
| Metadata held | sha256 6402bfa61866406540f67e37a4f2468ca779c48b3e886724c4cdc6e6a88c12f4 · 266 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 9dbf908e82c3511f36e6ba0da467688aee62e6308e2126b5789e6889656b3125 · 10,482 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 21:08 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.