Starship
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.
noteOnly 1.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 13:48 UTC |
| Creator | 7ACLDJChbo4eACPuwf9MKziTVQbwwyWzNxNjr5hJG7Jc |
| Creator took | 6.6% of supply in the first block |
| Outside buyers | 16 distinct wallets, not counting the creator, bought on the bonding curve: 12 within the first 30s, 4 bundled into the creation block. |
| Graduated | 57 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 | not while we watched |
| Recorded from | f3oyYp8SN2J1bb6sT7tRb7… slot 451,337,000
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-28 13:48:26 UTC Slot 451,337,000, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 12 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-28 14:45:41 UTC +57m 15s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-28 14:45:41 UTC +57m 15s
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 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 27 launches from 18 creator wallets, including this one. See them → |
Pool
| Liquidity | 1.9 SOL |
| Read from chain | 2026-09-28 16:59 UTC, just now |
What this launch claimed to be
| Name | Starship |
| Description | Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → |
| Metadata held | sha256 d35ef8b67dfb5df7581d9195a2698d40b045eedf3545387bbc7418c5a9972d45 · 472 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 30cf283b8c4bd937fb5c77f076f700e596e5e832d9e14f1c906080b1b5004e40 · 447,630 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 13:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.