Also recorded, and not part of the finding above: this creator has 9 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. They are listed under Seen before, further down this page.
At launch
| Created | 2026-11-10 19:57 UTC |
| Creator | GUn1VKhSWfCjkjtUKww6ikrCAZqwKdXRcYCM2vzgBfCr |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 3 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: 4 within the first 30s, 2 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. |
| Graduated | not while we were watching |
| Curve on chain | Nothing 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 sold | not while we watched |
| Recorded from | 95spsJMonDZSFHC6i39m3F… slot 467,846,150
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-10 19:57:23 UTC Slot 467,846,150, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-11-10 19:57:23 UTC +0s
2.890e-8 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 in | 4 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 picture | No other launch we hold a picture for used this one. |
| This creator | 9 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
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 | Amazon |
| Description | Added to cart. Common sense removed. 📦 Amazon Coin is an unofficial meme token for impulse shoppers, tracking-page refreshers, and everyone whose “one small order” became five deliveries. Your next questionable purchase has entered the chat. |
| Metadata held | sha256 fce8de8807bd836e8be83f42df103d63e3abbb1e8843371b9846d6fc81e921e6 · 505 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 4c618773ad061695f29f6d854f35e673e1c87b8dd0f7102f0169d15af651f6b5 · 14,954 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 19:57 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.