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

trap

Nobody bought its curveRead 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 8 other launches, all of them this same creator's, and this creator has 97 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, 14.4% of the launches whose picture we hold carry one only their own creator reused. 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.

7XTVfyR6C7aYbu6gKqckn18fMBXPjbgSAs4mqmJ3pump Solscan pump.fun

Cite this record as: Chain of Title, trap (2016houseparties), mint 7XTVfyR6C7aYbu6gKqckn18fMBXPjbgSAs4mqmJ3pump, observed at creation 2026-09-03 02:27 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/7XTVfyR6C7aYbu6gKqckn18fMBXPjbgSAs4mqmJ3pump

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.

findingIt completed its bonding curve with zero outside buyers on record.

At launch

Created2026-09-03 02:27 UTC
Creator3QsuQtczCa7WQQK7LvFu2m8CDFazzwqxmcVDUts6ZMpP
Creator took0.3% of supply in the first block
Outside buyers0 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: 0 within the first 30s, 0 in the very same block the token was created in.
Graduated15 min after launch
Curve on chainComplete. We read the bonding curve account 33.5 days ago and it was finished. Checked 2026-09-10 00:19 UTC.
Creator soldnot while we watched
Recorded from3aijaFLLsAuHoB9jAEgGP1… slot 443,856,544
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-09-03 02:27:00 UTC
Slot 443,856,544, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds inNo buyer, 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-09-03 02:42:13 UTC +15m 13s
Confirmed against the venue's own completion state.
Highest price seen2026-09-03 02:43:35 UTC +16m 35s
8.713e-11 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 pictureOn 9 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.4% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 201 launches from 44 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, 87.2% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 8 other launches, all of them this same creator's. Across the archive, 11.2% of the launches whose document we hold carry one only their own creator reused. See them →
This creator97 earlier launches, 18 confirmed complete on chain, 1 with findings on record. Across the archive, 70% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
Name2016houseparties
Metadata heldsha256 6688777fb2430988e4df9053904c04d0fc990c4292b9186d19f07dc2eacaa58d
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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-22 18:18 UTC.
Picture heldsha256 e1bdf292140dc3b8c7a4065e26ce5ccc4779af12f4ac6a63f3b856f4bce27f8e · 125,019 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-09-11 18:53 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