XCAT
The curve completed 22s 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 22s after launch.
noteOnly 1.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 21:53 UTC |
| Creator | AFBGQKHV3DRSZy3EYL6WUkqJv66BVLCNHRugxcaWT65V |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 64 distinct wallets, not counting the creator, bought on the bonding curve: 64 within the first 30s, 0 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 | 4GmZE2TVcXbxYAe66McD3a… slot 452,413,921
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 21:53:14 UTC Slot 452,413,921, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-10-01 21:53:37 UTC +22s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 64 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-01 22:00:06 UTC +6m 52s
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 | On 7 launches from 7 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 428 launches from 321 creator wallets, including this one. See them → |
| This document | Byte-identical to 3 other launches' metadata document. See them → |
| This creator | 5 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 19 other creator wallets, across 17 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.6 SOL |
| Read from chain | 2026-10-02 05:31 UTC, just now |
What this launch claimed to be
| Name | xcat |
| Metadata held | sha256 aff0a527c27f4ca7052fdf5667410d96790c28a4a2ace9eae5cd7a10747c622e · 252 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 36fbfa4b3e3168ebb2bbd1eb2d4c060a0b0514d4c7d7dd302408532aa094417a · 168,236 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 21:53 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.