Jackass
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.
At launch
| Created | 2026-10-01 05:52 UTC |
| Creator | H1b8xmNYH9fVFyY8DE3YfCewXBrsMb15DwgeGzTxnA4E |
| Creator took | 23.0% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | in the same batch of events as the 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 recorded - this venue's trades do not name the wallet |
| Recorded from | WpQVaJzvuTzzN6BwDrGRT1… slot 452,198,671
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. |
Order of events
| Created | 2026-10-01 05:52:40 UTC Slot 452,198,671, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-01 05:52:40 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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 42 launches from 34 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
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 | Jackass Coin |
| Description | Pump AMM |
| Metadata held | sha256 de70ffb7349555da7b2e7f47671138b0bae80b3d7a167f5d1c2aea838440c22b · 227 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 51a857275638db05dcb62895891cbe9325eb9116c69a3b1b17df9a3def362d33 · 267,938 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 05:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.