NVDA
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.
At launch
| Created | 2026-09-22 19:15 UTC |
| Creator | BYgRJEGGyh9JfYF2u7cfJttMVsPmoToma9WbY1CLioaC |
| Creator took | 79.3% of supply in the first block |
| Outside buyers | 0 distinct wallets, not counting the creator, bought on the bonding curve: 0 bundled into the creation block. |
| Graduated | yes; we did not record when |
| Curve, read on chain | Complete. We read the bonding curve account 3.9 h ago and it was finished. Checked 2026-09-22 19:16 UTC. |
| Creator sold | not while we watched |
| Recorded from | 5c7AAnyTYdehs2KD5pAy9r… slot 449,470,084
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | snap30_buyers - no thirty-second snapshot was taken, and that snapshot is meaningful only for an observed launch.
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
| Created | 2026-09-22 19:15:40 UTC Slot 449,470,084, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-09-22 19:15:40 UTC
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. |
| Curve completed | Recorded as complete; we did not record when.
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 picture | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 174 launches from 149 creator wallets, including this one. See them → |
Who took the curve
One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
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
| Name | NVIDIA |
| Metadata held | sha256 c799cca4e937ecad0976221df35b06047ddefee7ecbb78b1530ad462542996d3 · 150 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 held | sha256 e467e7e617c6c45d5e70b57acdf039e363c1c3766af46b8b707a4090214a6832 · 7,540 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 19:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.