3,678,956 launches on record
Coverage from 2 Sep 2026
Archive read 16:48 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-15 14:49 UTC

AMAZON

Amazon.com, Inc.

RQ9CU8pBn7Ty379D596EExmTy3jAJHdY7saNpdwpump Solscan pump.fun

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

0.0%of supply taken by the creator in the first block
5outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed in the same batch of events as the 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 92 other launches from 88 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.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

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 5 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteTook 2 bonding curves outright. 83 SOL spent on curves. We hold no market trades for it in either direction, so what it did with the tokens afterwards is not on our record.

At launch

Created2026-11-15 14:49 UTC
CreatorMhHekYXzyba22jHdLSXieod8mWRV3mm2DnQkMFewPMr
Creator took0.0% of supply in the first block
Outside buyers5 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: 5 within the first 30s, 5 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.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 3.4 h ago and it was finished. Checked 2026-11-15 15:02 UTC.
Creator soldnot while we watched
Recorded from5G4MT1kcbY4sD6JeoGZbrD… slot 469,768,893
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-15 14:49:05 UTC
Slot 469,768,893, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-15 14:49:05 UTC +0s
Confirmed against the venue's own completion state.
Highest price seen2026-11-15 14:49:05 UTC +0s
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.
Thirty seconds in5 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.

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 92 launches from 88 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 556 launches from 515 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.7% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 96 other launches, across 93 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

Who took the curve

One transaction bought 42 SOL of this curve, 0 min after launch, from a wallet other than the creator's. The wallet and the transaction →

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
NameAmazon.com, Inc.
DescriptionWhile Amazon is historically the quintessential Web2 giant, the company actively captures massive market share in Web3 by acting as the primary infrastructure layer. Rather than issuing volatile native cryptocurrencies, Amazon leverages its massive cloud ecosystem, Amazon Web Services (AWS), to power decentralized networks, decentralized finance (DeFi) platforms, and crypto nodes.
Metadata heldsha256 b168d5947adf4448912dce2704f754111774ba3d979d6cabfcbb6d26a1f699f9 · 582 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 1f7fdef99ddb78283241203f49f8e52aeeb46e7472a54e27a4f97c30208ac3b7 · 3,195 bytes

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