PARAJAK
The curve completed 17s 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 17s after launch.
noteOnly 1.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 13:09 UTC |
| Creator | 961hoDUaFexbM2NWzX4cu3JrLKcyUGbWTtnLtymo5vjn |
| Creator took | 0.1% of supply in the first block |
| Outside buyers | 11 distinct wallets, not counting the creator, bought on the bonding curve: 11 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | pMauwA6bp8rJ4P6bzLLeBX… slot 452,619,399
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 13:09:28 UTC Slot 452,619,399, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 13:09:46 UTC +17s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 11 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. |
| Highest price seen | 2026-10-02 13:20:55 UTC +11m 27s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. 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 | 1.1 SOL |
| Read from chain | 2026-10-02 20:06 UTC, just now |
What this launch claimed to be
| Name | PARAJAK |
| Metadata held | sha256 8ce3f975c7c8e71ab0cdf9912fdbaecb86ad30e1d49a6faa31f009aeaa411a08 · 265 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 e3294a2fe87d5561415638ba2cebfa4b8f6224c4e61ccd9f4efaa2481a5f8735 · 1,034,170 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 13:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.