Cateoween
The curve completed 33s 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 33s after launch.
noteOnly 3.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-27 21:13 UTC |
| Creator | SMtpnGBqzRT8FFBehFiCCzj3CgvYcJRuQnqfpuBTFgd |
| Creator took | 5.0% of supply in the first block |
| Outside buyers | 131 distinct wallets, not counting the creator, bought on the bonding curve: 108 within the first 30s, 13 bundled into the creation block. |
| Graduated | 1 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 | 2vPVJKuAAcfkdXCqre1aM4… slot 451,114,498
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-27 21:13:51 UTC Slot 451,114,498, which is the chain's own clock for this moment. |
| Creation block | 13 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 108 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-09-27 21:14:24 UTC +33s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-27 21:14:24 UTC +33s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 7 launches from 7 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.4 SOL |
| Read from chain | 2026-09-27 23:10 UTC, just now |
What this launch claimed to be
| Name | Cateoween |
| Description | As everyone knows Cate is going to multi billions, and we need a seasonal derivative for it that is live on PumpFun I have over 300+ viewers right now on TikTok https://www.tiktok.com/@xrpbrian/live This is for the Cate Whales and the people who weren't able to get into Cate early I am going to be live on PumpFun everyday pushing Cateoween and making videos and content about it We will build the #1 community of strong holders, we will bring together all Cate Holders and have the bes |
| Metadata held | sha256 f2b6a88f107308d47e195e16f9fb78d36becb23a962975efc39ba54009b7035a · 1,079 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 2928b2d79eaca9c9544b6e81141e61770d203aad9a8791441b33b5fdd6c550aa · 418,532 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-27 21:13 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.