1,488,186 launches on record
Coverage from 2 Sep 2026
Archive read 21:53 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

FHC

The curve completed 6s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 803 other launches from 234 creator wallets in all, and this creator has 111 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, 46.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

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.

61zfdLDgXFmL5RsKFQMR1Z3Eam4YCvcUTR6AiBZApump Solscan pump.fun

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 8 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 6s after launch.
noteOnly 0.4 SOL of liquidity was in the pool just now.

At launch

Created2026-10-06 13:56 UTC
CreatorBhgmNapJBwXCdoYLvG1kytc3w8YF2K6gYPUkbCcMM2jN
Creator took0.2% of supply in the first block
Outside buyers8 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: 3 within the first 30s, 0 in the very same block the token was created in.
Graduated0 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 from4TWXj3mLPXefyGVeLUfKMH… slot 453,921,507
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.

Order of events

Created2026-10-06 13:56:55 UTC
Slot 453,921,507, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-06 13:57:01 UTC +6s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-06 13:57:01 UTC +6s
1.274e-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 in3 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 pictureOn 804 launches from 234 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 46.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 784 launches from 234 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, 86.4% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 765 other launches, across 226 creator wallets in all. Across the archive, 23.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator111 earlier launches, 6 confirmed complete on chain. Across the archive, 71.6% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group of 3 creator wallets in all. Across the archive, 57.8% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity0.4 SOL
Read from chain2026-10-06 22:32 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameFreakHouse
Metadata heldsha256 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 heldsha256 d96e930d0978f0db437d3825a82af4a350156be1c0ccce3ebef695c4b2cc7d41 · 146,969 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-06 13:56 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