terrafying
Checked, no markers foundWe watched this launch and checked it against every marker we record. None of them is present: the creator kept 1.4%, 278 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. A statement about what we checked, not a judgement about the token.
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-09-30 10:33 UTC |
| Creator | DFcxKCSZskfZXJFajZPiJfeyjdE94M5cutWxPqz1s9Xw |
| Creator took | 1.4% of supply in the first block |
| Outside buyers | 278 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 2 bundled into the creation block. |
| Graduated | 25 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 | 2cxsjREMjiUGXX8ssX4Jpc… slot 451,938,814
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 10:33:24 UTC Slot 451,938,814, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 10 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 10:58:42 UTC +25m 18s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 10:58:42 UTC +25m 18s
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 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 10 launches from 10 creator wallets, including this one. See them → |
| This creator | 2 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 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 | 67.6 SOL |
| Read from chain | 2026-09-30 16:45 UTC, just now |
What this launch claimed to be
| Name | ai torture chamber |
| Metadata held | sha256 8062cd9cffce479c35c330e12432a3ff4e34f9a9ca0dc0e7a3f21bf01448a9e1 · 418 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 72bef50801f8db419237d33bd906d032bccf951836522adbc1c22fa8e7a47aab · 32,994 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 10:33 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.