78
The curve completed 8s 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 8s after launch.
noteThe creator sold while we were watching.
noteOnly 0.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 06:47 UTC |
| Creator | tQZUzqMsbWPmbAJGms87vMpa4GUs17hjXNw1k1DxYfS |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 41 distinct wallets, not counting the creator, bought on the bonding curve: 14 within the first 30s, 0 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 | 5sumr4SmzGHth8CQEQ5Dyh… slot 451,888,058
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 06:47:29 UTC Slot 451,888,058, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-30 06:47:37 UTC +8s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 14 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. |
| Highest price seen | 2026-09-30 06:48:12 UTC +43s
8.444e-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 2 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 6 launches from 4 creator wallets, including this one. See them → |
| This creator | 34 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.2 SOL |
| Read from chain | 2026-10-01 12:58 UTC, just now |
What this launch claimed to be
| Name | Ship 78 Moon Landing |
| Description | “Peace Ship” 78 moon landing 🛬 |
| Metadata held | sha256 017933413e23de8f06604745e33bcea7ce8f8c0464dc8aa6ea375af297dd1d8e · 363 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-10-01 06:47 UTC. |
| Picture held | sha256 792d9d9f05efc515085af8b6884d09b1f1e93d9f312c78432bd19d71fb3fff78 · 2,201,304 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 06:47 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.