SAW
The curve completed 13s 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 13s after launch.
At launch
| Created | 2026-09-30 17:03 UTC |
| Creator | 2syAkjKjCZeYFer7xPfYJjCJGbnUoB5NLJxqpaV3Zn1o |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 84 distinct wallets, not counting the creator, bought on the bonding curve: 84 within the first 30s, 3 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 | 2tyCb363phvoc4pBoKZJfN… slot 452,026,329
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:03:48 UTC Slot 452,026,329, 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. |
| Curve completed | 2026-09-30 17:04:01 UTC +13s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 17:04:01 UTC +13s
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 | 84 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 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 40 launches from 31 creator wallets, including this one. See them → |
| 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 | 108.8 SOL |
| Read from chain | 2026-09-30 22:06 UTC, just now |
What this launch claimed to be
| Name | Clanker Torture Chamber |
| Description | Ending the PVP with my own. Support infinite clanker torture! |
| Metadata held | sha256 29b0d4d0fedd7fb24170dfc27d31e9968df701c4b110071cbae17d345f1a87d9 · 439 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 35b42be8c0f1d2cdcea36225acdb0d5c681a5b71df5a51ba86814bf6de06d4bb · 7,753 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 17:03 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.