CASHTAG
The curve completed 14s 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 14s after launch.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-22 02:12 UTC |
| Creator | jKZzdnkC6RvvyvYy8J7un2y7WYZMJF5WinT28hJNNh6 |
| Creator took | 6.6% of supply in the first block |
| Outside buyers | 192 distinct wallets, not counting the creator, bought on the bonding curve: 192 within the first 30s, 15 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 | w3wSaT8jwHqnni8t2sXaPB… slot 449,240,254
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-22 02:12:40 UTC Slot 449,240,254, which is the chain's own clock for this moment. |
| Creation block | 15 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-22 02:12:54 UTC +14s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-22 02:12:54 UTC +14s
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 | 192 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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 55 launches from 51 creator wallets, including this one. See them → |
| This document | Byte-identical to 13 other launches' metadata document. See them → |
Pool
| Liquidity | 74.2 SOL |
| Read from chain | 2026-09-22 13:24 UTC, just now |
What this launch claimed to be
| Name | Cashtag |
| Description | Launch tokens from X paired with a stock through a hashtag. |
| Metadata held | sha256 e1dfb0e3e5e5493bc61fa34d547a9060725711686d938d01c2f514e9b6a32d9d · 318 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 a9a1acf87e0d37ee725ef058d82b115a33341c5e3ddb1070ab9b39f7f5558c15 · 13,630 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 02:12 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.