3,462,049 launches on record
Coverage from 2 Sep 2026
Archive read 03:18 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

NVIDIA

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 433 other launches from 431 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.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.

5XwEc6rbgSYJ6PRMATiVRqXZEHXD8Syi69NSUdz9pump Solscan pump.fun

Cite this record as: Chain of Title, NVIDIA, mint 5XwEc6rbgSYJ6PRMATiVRqXZEHXD8Syi69NSUdz9pump, observed at creation 2026-11-11 02:51 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/5XwEc6rbgSYJ6PRMATiVRqXZEHXD8Syi69NSUdz9pump

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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

At launch

Created2026-11-11 02:51 UTC
CreatorGc75N4UrEH6qZuqWC29dWryfCEaovgRkL2eye15dF9VB
Creator took0.0% of supply in the first block
Outside buyers6 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.
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 soldno
Recorded from5X5qGnpZ4xaLS13xgr8dtw… slot 467,962,059
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-11 02:51:27 UTC
Slot 467,962,059, 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.
Curve completed2026-11-11 02:51:32 UTC +6s
Confirmed: a PumpSwap pool was found for it.
Thirty seconds in6 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.
Highest price seen2026-11-11 02:55:24 UTC +3m 58s
6.258e-7 SOL per token. Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a decoded one. 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 433 launches from 431 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 1,029 launches from 910 creator wallets. 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.5% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 5 other launches, across 6 creator wallets in all. Across the archive, 33% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

Pool

Liquidity0.6 SOL
Read from chain2026-11-11 09:15 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameNVIDIA
DescriptionThe official handle for NVIDIA.
Metadata heldsha256 00c61017cb302b5182363cb0c75510b4ae009e7932d9a3c0d7a812078400f55f · 376 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 006d9299e1c6922d85b4e4366ecc21867029712fbd207f857327bf9376eab42d · 8,898 bytes

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