Its own first blocks
0.2%of supply taken by the creator in the first block
5outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingOnly 5 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 2.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-11-22 11:29 UTC |
| Creator | DgtxZZDdbuuE75xpDZrjmRoM4eLk52VjepLuX8kJ9BzC |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 5 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: 5 within the first 30s, 5 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 0 min after launch |
| Curve 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 | not while we watched |
| Recorded from | Z9tRiABC2U1u9L3J3mRctc… slot 472,524,423
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-22 11:29:32 UTC Slot 472,524,423, 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. |
| Curve completed | 2026-11-22 11:29:33 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-22 11:29:33 UTC +0s
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. |
| Thirty seconds in | 5 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 | No other launch we hold a picture for used this one. |
Pool
| Liquidity | 2.3 SOL |
| Read from chain | 2026-11-22 16:55 UTC, just now |
What this launch claimed to be
| Name | HOMERJAK RETREAT |
| Description | |
| Metadata held | sha256 db032371ce4b60416e55c8686d605b3c7580ea151d54ce9cdfc71bcf2a3dceb7 · 321 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 2e66cc837c38aae08ae18a69ebc207c12406bfa53232b8ff505c4299b9fb38be · 92,803 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-22 11:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.