SpaceSexy
Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 45.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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.
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-10-04 19:34 UTC |
| Creator | DG2ejCQZ52FFERzUXMnaaii3RQUfM69HSmo8oHdZ1cQ2 |
| Creator took | 19.9% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else. |
| Graduated | in the same batch of events as the launch |
| Curve 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 recorded - this venue's trades do not name the wallet |
| Recorded from | 5JMmWSmXJMR1HRGePHzZ5C… slot 453,351,844
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Keep this launch as a document
A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.
No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.
Order of events
| Created | 2026-10-04 19:34:43 UTC Slot 453,351,844, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-04 19:34:43 UTC Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
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 6 launches from 5 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. See this ticker's page → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | SpaceXSI |
| Metadata held | sha256 e191b5d127b4527eacee59302ddc99a60c56199f9ae0c50f90ee4908abada33f · 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 9018ef1b2ee335a5c1974a8383861377969c8ffb7e920b0ca2935b2f2c4ec796 · 1,836 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-04 19:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.