Charlie
The curve completed 59s 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.
noteThe creator took 30.4% of supply at launch.
findingIt left the curve 59s after launch.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-26 22:25 UTC |
| Creator | bwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa |
| Creator took | 30.4% of supply in the first block |
| Outside buyers | 456 distinct wallets, not counting the creator, bought on the bonding curve: 312 within the first 30s, 2 bundled into the creation block. |
| Graduated | 1 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 | 4PZEpXvTAQus562TjNghau… slot 450,808,140
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-26 22:25:01 UTC Slot 450,808,140, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 312 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. |
| Curve completed | 2026-09-26 22:25:59 UTC +59s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-26 22:25:59 UTC +59s
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. |
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 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 81 launches from 65 creator wallets, including this one. See them → |
| This creator | 5,424 earlier launches, 187 confirmed graduated on chain, 46 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2,130 other creator wallets, across 4,495 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 | 86.7 SOL |
| Read from chain | 2026-09-27 04:28 UTC, just now |
What this launch claimed to be
| Name | Charlie |
| Description | Fees to @jon via UsePaid |
| Metadata held | sha256 45ec6d21664d498eb73483191cfdaa03657eaa33b7a0bc3960f3b5c51da84f6c · 292 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 83ad07a5abe87d46165d28b5156a07e6b64602b116406b714e08c94b04c44300 · 13,973 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-26 22:25 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.