Mochi
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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 sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 12:48 UTC |
| Creator | 9QznKKTqDsyr4ALe4dira6Vjzy4WLW7tYfTtcbVLJ9w9 |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 275 distinct wallets, not counting the creator, bought on the bonding curve: 33 within the first 30s, 0 bundled into the creation block. |
| Graduated | 7 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 | GDHGUqbUosTFn9x7wncjVG… slot 451,969,154
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 12:48:29 UTC Slot 451,969,154, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-09-30 12:48:29 UTC
0.000e+0 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 | 33 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-30 12:55:45 UTC +7m 16s Confirmed: a PumpSwap pool was found for it. |
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 27 launches from 20 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 157 launches from 92 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 2 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 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 | 0.0 SOL |
| Read from chain | 2026-09-30 22:06 UTC, just now |
What this launch claimed to be
| Name | Mochi |
| Description | Created on https://rapidlaunch.io |
| Metadata held | sha256 6030d2bdf1135c011e6d37bc9464c5a700be278b4fa7f0ec7d1dbcf58b1824b4 · 402 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 30c1a2957bbbeeaa8cd3090ff78245de55f4775bd47ae57bcb2824235074d5af · 20,614 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 12:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.