Launch record · observed at creation 2026-11-09 04:53 UTC
Kraken
krakenfx
Also recorded, and not part of the finding above: this picture is on 79 other launches from 75 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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-11-09 04:53 UTC |
| Creator | FLx7YiT5L4dYnrZxzXU1Nrnbhhcc1Pm8NAJggnRMqU8z |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown 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. |
| Graduated | in the same batch of events as the launch |
| Curve 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 recorded - this venue's trades do not name the wallet |
| Recorded from | jKyZ9YFoJea1Hwpd8YWXQJ… slot 467,190,242
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-11-09 04:53:01 UTC Slot 467,190,242, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-09 04:53:01 UTC Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
Seen before
| This picture | On 80 launches from 75 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 179 launches from 166 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 61 other launches, across 62 creator wallets in all. Across the archive, 33% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 61 other creator wallets, across 1 shared file, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group of 62 creator wallets in all. Across the archive, 64% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
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 | krakenfx |
| Metadata held | sha256 51f92c7bca632600b1d19a4cd5b646fe0a74d81e96bff1febb925fd25f5d8199 · 412 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 6b6367472d7acd151bebcf08cb9af9e56680a6fc028bff9303c9b5c189dfdf34 · 7,014 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-09 04:58 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.