BANDIT
The curve completed 9s after 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.
findingIt left the curve 9s after launch.
At launch
| Created | 2026-09-30 18:40 UTC |
| Creator | 7UkWDt4HMiaPAZphkV7NxSy9Pf2Mtc1LdxFADK5KaYe1 |
| Creator took | 4.9% of supply in the first block |
| Outside buyers | 153 distinct wallets, not counting the creator, bought on the bonding curve: 153 within the first 30s, 16 bundled into the creation block. |
| Graduated | 0 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 | 3H9J3X4aJr5VPLXv8tEzVr… slot 452,048,083
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 18:40:58 UTC Slot 452,048,083, which is the chain's own clock for this moment. |
| Creation block | 16 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-30 18:41:08 UTC +9s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 18:41:08 UTC +9s
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. |
| Thirty seconds in | 153 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. |
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 51 launches from 51 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 156 launches from 120 creator wallets, including this one. See them → |
| This document | Byte-identical to 49 other launches' metadata document. See them → |
Pool
| Liquidity | 346.3 SOL |
| Read from chain | 2026-09-30 23:15 UTC, just now |
What this launch claimed to be
| Name | The PumpFun Heist |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 844486e151bc27292fca4345f77679fc2a0e2051b1df278aed735944d5e42ec1 · 478 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 db1fa9111f9159e2b39ebedf8cc9df5496bb18b10687346ab302bc71091e9fc5 · 361,506 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 18:40 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.