FIX6900
The curve completed 56s 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 56s after launch.
noteThe creator sold while we were watching.
noteOnly 5.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 22:20 UTC |
| Creator | 9aztChMYbsF5HRFG2ECkjfEdHHZChB1b3tRHQ2TPgKjv |
| Creator took | 15.3% of supply in the first block |
| Outside buyers | 263 distinct wallets, not counting the creator, bought on the bonding curve: 168 within the first 30s, 11 bundled into the creation block. |
| Graduated | 1 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 | yes |
| Recorded from | 3zC14yPjhx2Quwri98mcaT… slot 452,420,058
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 22:20:49 UTC Slot 452,420,058, which is the chain's own clock for this moment. |
| Creation block | 11 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 168 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 22:21:46 UTC +56s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 22:21:46 UTC +56s
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 193 launches from 71 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 743 launches from 319 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 601 earlier launches, 75 confirmed graduated on chain, 14 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 399 other creator wallets, across 585 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 | 5.8 SOL |
| Read from chain | 2026-10-02 05:32 UTC, just now |
What this launch claimed to be
| Name | Fantasy Index 6900 |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 62c810b2fabe129e93d535073badb285a94d8bb72e4168eea4a9ad984b4a83c6 · 467 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 5ad575c8bd52dc736f0ccc8175b287a73e63a6046a36e2df6a2e04ef8dc85a58 · 48,648 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 22:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.