Pain
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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 sold while we were watching.
At launch
| Created | 2026-09-30 11:18 UTC |
| Creator | 36A6mEN5rYJdVTb6fMqVvG6ez8g2mTYdr1omWcQ1kDKG |
| Creator took | 8.2% of supply in the first block |
| Outside buyers | 792 distinct wallets, not counting the creator, bought on the bonding curve: 175 within the first 30s, 10 bundled into the creation block. |
| Graduated | 39 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 | 52o6tXMxZtt6p5R4PiUpaE… slot 451,948,883
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 11:18:13 UTC Slot 451,948,883, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 175 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 11:57:30 UTC +39m 17s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 11:57:30 UTC +39m 17s
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 18 launches from 15 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 72 earlier launches, 1 confirmed graduated on chain, 1 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 18 other creator wallets, across 29 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 | 40.6 SOL |
| Read from chain | 2026-09-30 16:40 UTC, just now |
What this launch claimed to be
| Name | The Pain Axis |
| Description | Launched on discord.gg/uxento |
| Metadata held | sha256 b28c6c5d633525a2aee8ff694ac65be2e6ea126a320b682988ee5a3267c392c8 · 340 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 5743caf29a54baa7cc31440932bdb8e49adff625ea58bda241fe6ddf828babb0 · 15,062 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 11:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.