Ajax
The curve completed 24s 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.
noteThe creator took 30.4% of supply at launch.
findingIt left the curve 24s after launch.
At launch
| Created | 2026-10-01 02:23 UTC |
| Creator | 5ZUz3HuBAG9QdJgZR2mCKYJ2fBLaj8g2wSoJ8ysUQ1GN |
| Creator took | 30.4% of supply in the first block |
| Outside buyers | 115 distinct wallets, not counting the creator, bought on the bonding curve: 115 within the first 30s, 2 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 | 266figyiFzCvhRUB5hZJbf… slot 452,151,568
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 02:23:07 UTC Slot 452,151,568, 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. |
| Curve completed | 2026-10-01 02:23:31 UTC +24s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 02:23:31 UTC +24s
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 | 115 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 110 launches from 55 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 104 launches from 62 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
Pool
| Liquidity | 392.6 SOL |
| Read from chain | 2026-10-01 06:09 UTC, just now |
What this launch claimed to be
| Name | Ajax |
| Metadata held | sha256 c3988c816359610da029b9dcc2ad41b66bfe1b1cb00e430a779d3b2ae10272e9 · 308 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 f58e86303c5feafe32af4181524434868ec7edc4d05f9d1aecf7e9e00559ae74 · 1,864 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 02:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.