GROK
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.
6HU4CmRb15C2nQDx8Ld2f2W2wTdmog6aZiiXdrT5Pzi8
Solscan
not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
At launch
| Created | 2026-09-21 18:44 UTC |
| Creator | 7naFFwuEJWeWwWYQUkgAWHsxYKg3KctEuUj42JdAMidP |
| Creator took | 12.4% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 10 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 recorded - this venue's trades do not name the wallet |
| Recorded from | 3Rrz7s7CYHZWkCaX9vSLuA… slot 449,139,661
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.
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-09-21 18:44:53 UTC Slot 449,139,661, which is the chain's own clock for this moment. |
| Highest price seen | 2026-09-21 18:44:53 UTC
0.000e+0 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-21 18:54:32 UTC +9m 40s Confirmed against the venue's own completion state. |
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 135 launches from 67 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 625 launches from 378 creator wallets, including this one. See them → |
| This document | Byte-identical to 5 other launches' metadata document. See them → |
| This creator | 582 earlier launches, 15 confirmed graduated on chain, 4 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 289 other creator wallets, across 472 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. 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 | Grokification |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 b027b85df1d971e585587cef902a2f448af6c161b3970fa991375d594523350c · 466 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-22 18:46 UTC. |
| Picture held | sha256 0881f0c8f8e03bcc30f82adb8c217a3dd9297289f840931977adf21922f81489 · 15,506 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-21 18:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.