BI
The creator took 30% of supply at 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.
noteThe creator took 30.4% of supply at launch.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-30 17:12 UTC |
| Creator | bwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa |
| Creator took | 30.4% of supply in the first block |
| Outside buyers | 184 distinct wallets, not counting the creator, bought on the bonding curve: 54 within the first 30s, 3 bundled into the creation block. |
| Graduated | 1 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 | 4c96hZDA3kzdnm9mSb4BEy… slot 452,028,287
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 17:12:33 UTC Slot 452,028,287, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 54 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-30 17:13:49 UTC +1m 16s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 17:13:49 UTC +1m 16s
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 37 launches from 22 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 260 launches from 200 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 6,442 earlier launches, 223 confirmed graduated on chain, 46 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2,491 other creator wallets, across 6,254 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 50.6 SOL |
| Read from chain | 2026-09-30 22:39 UTC, just now |
What this launch claimed to be
| Name | Butthole Intelligence |
| Metadata held | sha256 cd12c011b77962a99e640a25426d8a63ab2edbddfdf68ce4900528fa9ce16ce7 · 347 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 d6dc71b81b1f4877f0dff14c5c119f9894d8b01f9a0bac7b36522f1fb8af9eb9 · 11,394 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 17:12 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.