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

HOUSECOIN

The creator took 30% of supply at 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 2 other launches from 2 creator wallets in all, and this creator has 7,103 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, 44.2% 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.

6rpHWXkQwC2GePVi9Qd6sNRzhcsNqk4S8vAaDBhDdbHR Solscan

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.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
noteThe creator took 30.4% of supply at launch.

At launch

Created2026-10-02 20:04 UTC
CreatorbwamJzztZsepfkteWRChggmXuiiCQvpLqPietdNfSXa
Creator took30.4% of supply in the first block
Outside buyersunknown 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.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldnot recorded - this venue's trades do not name the wallet
Recorded from4ASF51mTPm4f5VP4DD8fF3… slot 452,712,364
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

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-02 20:04:16 UTC
Slot 452,712,364, which is the chain's own clock for this moment.
Highest price seen2026-10-02 20:04:16 UTC
0.000e+0 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 pictureOn 3 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 32 launches from 21 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. See this ticker's page →
This documentThe same launch document, byte for byte, as 2 other launches, across 2 creator wallets in all. See them →
This creator7,103 earlier launches, 248 confirmed complete on chain, 46 with findings 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,751 other creator wallets, across 7,711 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. See the linked wallets →

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
NameHouse Coin
Metadata heldsha256 9538a5343320fcbe23110d7be160ea2591c2f0aaf98d2ee240b49cc24ffe48f5 · 474 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 f35acb793d94dc1e55fc739f7a52fd43501bc18295a48633e186bbdaa249257d · 16,800 bytes

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