CSW
The curve completed 57s 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 57s after launch.
noteThe creator sold while we were watching.
noteOnly 21.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-19 02:24 UTC |
| Creator | 9z3SYLFaRMr7M5dC7F8DbaaGkMxaCofLYm6YvEmUqPan |
| Creator took | 6.6% of supply in the first block |
| Outside buyers | 30 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 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 | 64qNqB7ssRsX7MqkLpVekq… slot 448,271,276
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-19 02:24:05 UTC Slot 448,271,276, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| 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. |
| Curve completed | 2026-09-19 02:25:02 UTC +57s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-19 02:26:45 UTC +2m 40s
3.443e-6 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.
Pool
| Liquidity | 21.0 SOL |
| Read from chain | 2026-09-19 05:35 UTC, just now |
What this launch claimed to be
| Name | Chinese strange world |
| Description | Very strange Chinese affairs |
| Metadata held | sha256 70fdc4e6687d94cfbe4aba8ba36e99abb03b8a2e4e792706522e1ee58a479da2 · 230 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 | Not captured, so we cannot show what it published. That is our storage budget, not a finding about the launch. |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-19 02:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.