3,557,778 launches on record
Coverage from 2 Sep 2026
Archive read 02:56 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-12 14:02 UTC

NVDIAHOUSE

NVIDIA HOUSE COIN

EVWBXYnaNZQEZmZYwrkNhzomM6jmd6HH1Ly8cVaRpump Solscan pump.fun
0.2%of supply taken by the creator in the first block
89outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
2launches carry this ticker, from 2 creator wallets
1other launch declared this same launch document, byte for byte
1other launch used this exact picture file
Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 0.2%, 89 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

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

At launch

Created2026-11-12 14:02 UTC
Creator9fLwvJZVNhSGRXpMUkpjHM3P1nc7ng1Gmk8GZF3pUyps
Creator took0.2% of supply in the first block
Outside buyers89 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: 17 within the first 30s, 6 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.
Graduated3 min after launch
Curve on chainComplete. We read the bonding curve account 14.6 h ago and it was finished. Checked 2026-11-12 14:30 UTC.
Creator soldnot while we watched
Recorded fromGGNuHLj4bG1zc3cnyM4mwR… slot 468,551,489
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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.

Order of events

Created2026-11-12 14:02:17 UTC
Slot 468,551,489, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in17 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-11-12 14:05:01 UTC +2m 44s
Confirmed against the venue's own completion state.

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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.4% of the launches whose picture we hold carry one a different creator also used. See them →
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, 89.6% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 33.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 1 other creator wallet, 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 2 creator wallets in all. Across the archive, 63.8% of launches come from a creator linked to at least one other wallet this way. 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
NameNVIDIA HOUSE COIN
Description
Metadata heldsha256 cc4e99fe60732aa59d01b468bea35f54b062895dc222d56b6244e2081d974d7d · 331 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 097e604abffbd151d69ff008931cffaa629f9d5c101880b28619c3e53eeec5a3 · 413,431 bytes

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