Also recorded, and not part of the finding above: this picture is on 3,015 other launches from 851 creator wallets in all, and this creator has 12 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, 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.
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-13 11:45 UTC |
| Creator | AKsxkvFe8FXcpev4Zna2uDzemYJ6hiB6sNEqEYMV5Y3T |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 15 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: 4 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 7.1 h ago and it was finished. Checked 2026-11-13 12:01 UTC. |
| Creator sold | yes |
| Recorded from | 3HZhA5gAYd9FMfW92jf7K4… slot 468,914,673
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-13 11:45:58 UTC Slot 468,914,673, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-11-13 11:46:24 UTC +25s Confirmed against the venue's own completion state. |
| Thirty seconds in | 4 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 3,014 launches from 851 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 2,851 launches from 836 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 → |
| This document | The same launch document, byte for byte, as 2,864 other launches, across 827 creator wallets in all. Across the archive, 33.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| This creator | 12 earlier launches. All 2 that reached the graduation threshold on our feed were read on chain, and none had completed. 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 | FreakHouse |
| Metadata held | sha256 8942166f884a0e45c8a20afa81fa0353fe21f4d43fcf2206c7e21a56221aaca3 · 191 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 d96e930d0978f0db437d3825a82af4a350156be1c0ccce3ebef695c4b2cc7d41 · 146,969 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-13 11:45 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.