BOOTY
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-03 04:39 UTC |
| Creator | 31swE8bYWmnoc36ufbMJEz7Q4k3ihtCAMKk133eUzAom |
| Creator took | 0.0% 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 | 2 min after 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 | 3ipXmM2x2wpWoUZs4PvT1y… slot 452,828,077
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-03 04:39:52 UTC Slot 452,828,077, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-03 04:42:08 UTC +2m 16s 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 | No other launch we hold a picture for used this one. |
| This ticker | On 101 launches from 57 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 | Boo-ty |
| Description | Prepare for a wild ride to the underworld of zero-calorie treasure—Boo-ty is the spooktacular cryptid that haunts your wallet and tickles your funny bone! 🍑 Fees → @bagspay: buybacks + airdrops to holders. |
| Metadata held | sha256 7a4a9b54b0cb9ca46276104c6e6bf145d9a4a4d9c713724cbbe35eaa21165c65 · 486 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 e0fd0e3c465f5751e4193945cad161044d07dd5cfbab04837a0453f8de11fe9d · 17,932 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-03 04:41 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.