reserve
The curve completed 21s 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 21s after launch.
noteOnly 3.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 02:52 UTC |
| Creator | E5SS33Yo9vKfw2gthG2QPuDdNhfrMR8PfXxpnbNGiXCU |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 259 distinct wallets, not counting the creator, bought on the bonding curve: 259 within the first 30s, 12 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 | 31GT3JYECVKuib3YvYMDEr… slot 452,158,083
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 02:52:16 UTC Slot 452,158,083, which is the chain's own clock for this moment. |
| Creation block | 12 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 02:52:37 UTC +21s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 02:52:37 UTC +21s
4.109e-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 | 259 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 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 4 launches from 4 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. 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 | 3.6 SOL |
| Read from chain | 2026-10-01 23:56 UTC, just now |
What this launch claimed to be
| Name | reserve |
| Metadata held | sha256 d695962746e96a62e90185c97baee1e0ba765192b1e7233241b77f59bd6d75e4 · 271 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 f94b14941bf1d9080416894dbb0b952272546079f701553a6d92a615b1e6f420 · 965,776 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 02:52 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.