HAUNTED
The creator took 30% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
noteThe creator took 29.8% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 8.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 21:24 UTC |
| Creator | DjM7Tu7whh6P3pGVBfDzwXAx2zaw51GJWrJE3PwtuN7s |
| Creator took | 29.8% of supply in the first block |
| Outside buyers | 606 distinct wallets, not counting the creator, bought on the bonding curve: 22 within the first 30s, 5 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | yes |
| Recorded from | 2mQqnVZyJhhSmFnbbgp1qF… slot 452,407,497
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 21:24:37 UTC Slot 452,407,497, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 22 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. |
| Curve completed | 2026-10-01 21:29:24 UTC +4m 47s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 21:29:24 UTC +4m 47s
4.109e-7 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. |
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 ticker | On 11 launches from 9 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 53 earlier launches, 11 confirmed graduated on chain, 2 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 21 other creator wallets, across 45 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
| Liquidity | 8.9 SOL |
| Read from chain | 2026-10-02 03:10 UTC, just now |
What this launch claimed to be
| Name | Haunted House |
| Description | Just a haunted house |
| Metadata held | sha256 6cdfac84414dba61e9e3c3fb9bc57d4eca51453085ce4e1e76b96059f80a0abf · 430 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 | Not captured, so we cannot show what it published. That is our storage budget, not a finding about the launch. |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 21:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.