Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-09-02 21:21 UTC |
| Creator | E8cgQqTrztQdPbsEJKzMQFRvLE1HHa2qM9C4bSwXTb2b |
| Creator took | 4.3% of supply in the first block |
| Outside buyers | 116 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 65 within the first 30s, 17 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | yes |
| Recorded from | yjCpA1shCF6ui6affNCfB5… slot 443,798,247
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-02 21:21:14 UTC Slot 443,798,247, which is the chain's own clock for this moment. |
| Creation block | 17 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 65 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-09-02 21:22:12 UTC +58s
1.858e-7 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. |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | CATALYST |
| Description | $CATALYST says every remembered coin needs the moment that starts reaction — post, meme, or one perfect finder 🧪 Tweet the CA, claim rewards, and become the reason everyone finally looks 👀 |
| Metadata held | sha256 5d8590b830064a1bc3da6c903bc0a8b3229edcbcfe146b01633aa4246dcb84f6 · 611 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 9184bc97f568194a623a82cf190404a746c3328d1c321345d325c76d5140396f · 65,518 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-11 00:14 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.