Also recorded, and not part of the finding above: this picture is on 3 other launches, all of them this same creator's, and this creator has 64 other launches on record. 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. 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-08 09:46 UTC |
| Creator | 4y6fDpAjwKJ4xkSYVbwHoqubhAqT1rQUHygbZA22ZSqp |
| Creator took | 0.9% of supply in the first block |
| Outside buyers | 2 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: 2 within the first 30s, 0 in the very same block the token was created in. |
| 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 | z9GrdYq4oiTrMxxKWyVCja… slot 466,869,768
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | 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-08 09:46:30 UTC Slot 466,869,768, 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 | 2 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. |
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 4 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 144 launches from 132 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 3 other launches, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them → |
| This creator | 64 earlier launches, 1 confirmed complete on chain. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
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 | Zig Coin |
| Description | Zig coin. the one and only. |
| Metadata held | sha256 6f4056e560b3bf2fbc434e91d3ad2a3e20cfe6d4c985abdf81af48f28781aec8 · 215 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 72efdb33a2403143d2438a9cdd6a921430cb21283f88a7293764052262367b0e · 18,339 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-08 09:46 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.