Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 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.4% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
At launch
| Created | 2026-11-12 08:07 UTC |
| Creator | CNCSy2NLi4ZtW33NcjbBurMHZ9XTW3oDBEF4iCBXJzHZ |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 14 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: 1 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 | not while we watched |
| Recorded from | 3k8guFDLEUAarmguvfMyh6… slot 468,452,477
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-12 08:07:43 UTC Slot 468,452,477, 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 | 1 distinct buyer, 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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.4% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 3 launches from 2 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.6% wear one that more than one creator wallet has launched. See this ticker's page → |
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 | dogwifihat |
| Description | dogwifihat on chads.fun |
| Metadata held | sha256 15ce0d7516024f58a086c62528cb527fff79c9c2e06f69528e928e79604fc8ed · 174 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 c978a97367076736a62d5c4e468125a75ac906b16db0f6c28b22fa6c0ca40e27 · 5,243 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 08:07 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.