HOTPEP
The curve completed 9s after 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.
findingIt left the curve 9s after launch.
noteOnly 1.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 14:37 UTC |
| Creator | HEpkhb57fAYF6y19VhT7BxwWit8Vm8XikahiSgQzzoKR |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 37 distinct wallets, not counting the creator, bought on the bonding curve: 37 within the first 30s, 8 bundled into the creation block. |
| Graduated | 0 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 | not while we watched |
| Recorded from | 3UsGDd4MgSx3DC6YmiTqfG… slot 452,639,304
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 14:37:45 UTC Slot 452,639,304, which is the chain's own clock for this moment. |
| Creation block | 8 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 14:37:53 UTC +9s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 37 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. |
| Highest price seen | 2026-10-02 14:42:53 UTC +5m 09s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 picture | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 19 creator wallets. See the linked wallets → |
Pool
| Liquidity | 1.5 SOL |
| Read from chain | 2026-10-02 18:11 UTC, just now |
What this launch claimed to be
| Name | HOTPEP |
| Metadata held | sha256 5cbf7aa2b5045e3dc5e1d233e407d51d5cef700f22cbc2d89665d2e677f8f4e9 · 305 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 0ba05b27b57911d09df29bc7a0d6fa40470948ac45bf27516f1036aa4332d6b1 · 124,157 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 14:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.