okitt
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.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-21 02:29 UTC |
| Creator | D6RwP6VdjCCYgGmnxDfJV6eJ26rwANHZMAkR98LCTo8N |
| Creator took | 1.7% of supply in the first block |
| Outside buyers | 26 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 0 bundled into the creation block. |
| Graduated | 2 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.2 days ago and it was finished. Checked 2026-09-21 02:41 UTC. |
| Creator sold | yes |
| Recorded from | 2QRofmbpPYtxjbmesi8eed… slot 448,920,422
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-21 02:29:17 UTC Slot 448,920,422, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 7 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-21 02:30:56 UTC +1m 39s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-21 02:30:56 UTC +1m 39s
1.289e-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 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This creator | 13 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-22 07:14 UTC, just now |
What this launch claimed to be
| Name | omega kitty |
| Metadata held | sha256 9caa8a341e2e25ec9acb1e1fd3eb51717e3faf52e959badf271514baf6ab1b6b · 194 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 6f85089d27e304a79bff75e074a0fdefc913272951e5b578ac69cab82b6ded94 · 184,971 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-21 02:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.