3/acc
Only 2 outside buyers bought its curveRead 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.
findingOnly 2 outside buyers bought on the bonding curve before it graduated.
noteOnly 1.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 01:22 UTC |
| Creator | 2bRoascfGCKkRnyZLmzJh7cKpiD45zyEzUmg9XPZzueC |
| Creator took | 3.5% of supply in the first block |
| Outside buyers | 2 distinct wallets, not counting the creator, bought on the bonding curve: 2 within the first 30s, 2 bundled into the creation block. |
| Graduated | 12 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 | 64exzcLqyygaotSJ2Tze3C… slot 452,137,967
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 01:22:24 UTC Slot 452,137,967, 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 | 2 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-10-01 01:34:41 UTC +12m 17s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 01:34:41 UTC +12m 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 36 launches from 23 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 13 launches from 11 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 1,758 earlier launches, 16 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 737 other creator wallets, across 1,262 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.8 SOL |
| Read from chain | 2026-10-01 07:28 UTC, just now |
What this launch claimed to be
| Name | 3/acc |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 a988a5e267a4088ec18d852bbd8e176db9ff544bfb2654dfa3eb213182bbc1b2 · 442 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 f35c982936674012721817dd9eac531e2e98ee9c6fab67670b57000969f785b9 · 32,068 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 01:22 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.