ZECAT
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteOnly 10.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-20 21:13 UTC |
| Creator | BeHUKrgzDTYWEE3oV5r2FBzTKGwt3sGVs9YUK5XUC79V |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 11 distinct wallets, not counting the creator, bought on the bonding curve: 9 within the first 30s, 26 bundled into the creation block. |
| Graduated | 1.1 h 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 | 3Lr2LHeAF22W8sW5d1G5Sk… slot 448,849,597
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-20 21:13:42 UTC Slot 448,849,597, which is the chain's own clock for this moment. |
| Creation block | 26 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 9 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-20 21:59:11 UTC +45m 30s
4.108e-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. |
| Curve completed | 2026-09-20 22:17:56 UTC +1h 04m 14s Confirmed: a PumpSwap pool was found for it. |
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 41 launches from 21 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 10.6 SOL |
| Read from chain | 2026-09-22 04:19 UTC, just now |
What this launch claimed to be
| Name | ZECAT |
| Metadata held | sha256 d67f24b4f79c1aeaf1a14b6d23c9cabf63d7e18a07996967255edb1bb194586c · 254 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 5bc304847cfde664e43c4e7d66064fbe59f8f38b4f921750f9b42fadcae8dae9 · 97,602 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-20 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.