2,302,443 launches on record
Coverage from 2 Sep 2026
Archive read 23 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

ALPENPEPE

Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

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.

HqHzo374kg1hvx7tFns8t4DWUf1ztHkotJUNcbzMpump Solscan pump.fun

Cite this record as: Chain of Title, ALPENPEPE (Alpenglow Pepe), mint HqHzo374kg1hvx7tFns8t4DWUf1ztHkotJUNcbzMpump, observed at creation 2026-10-23 06:28 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/HqHzo374kg1hvx7tFns8t4DWUf1ztHkotJUNcbzMpump

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.

noteOnly 3.2 SOL of liquidity was in the pool just now.

At launch

Created2026-10-23 06:28 UTC
Creator9hvVA1Tck9e9Y1Gchu8hH3KMNiJaUeuEkqNnmJCkFjVs
Creator took0.0% of supply in the first block
Outside buyers54 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: 28 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.
Graduated1 min after launch
Curve on chainNot 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 soldnot while we watched
Recorded from4ciEvytyw63ZF9xiFEAxih… slot 460,341,053
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-23 06:28:54 UTC
Slot 460,341,053, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in28 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 completed2026-10-23 06:30:03 UTC +1m 09s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-23 06:30:03 UTC +1m 09s
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 2 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, 88.1% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity3.2 SOL
Read from chain2026-10-24 03:24 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameAlpenglow Pepe
DescriptionAlpenglow pepe mode🏔
Metadata heldsha256 da2950c1870d66e107b7f9e7595fea4451c66d5c898684a2aadf7f0919b387d2 · 383 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 heldsha256 41a4702754d013a4f7815386dd2a94cb28087ae172f1cdd669801b5cb0df67e6 · 334,513 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-23 06:28 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another