Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's, and this creator has 1 other launch 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. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. They are listed under Seen before, further down this page.
At launch
| Created | 2026-11-12 22:25 UTC |
| Creator | GGsNG77QVZTkt6ZZsjVZRQfPFAXAKoxi4UyNuZJZJrAE |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 28 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: 15 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 5 min after launch |
| Curve on chain | Complete. We read the bonding curve account 5.2 h ago and it was finished. Checked 2026-11-12 23:00 UTC. |
| Creator sold | not while we watched |
| Recorded from | amurEAkBUhC5J2CoEiHEBT… slot 468,691,654
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-12 22:25:00 UTC Slot 468,691,654, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 15 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 seen | 2026-11-12 22:26:49 UTC +1m 49s
1.128e-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 | 2026-11-12 22:30:27 UTC +5m 27s 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 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 247 launches from 207 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 document | The same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them → |
| This creator | 1 earlier launch, none of which reached a graduation threshold while we watched. Across the archive, 70.6% 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 | Vice City coin |
| Description | Boys this is up to the community no massive sell we want the long term bag. GTA is gonna be for 15yrs minimum not only a one day hype… |
| Metadata held | sha256 415b727c423c1da398e424e07a772afb0d2c817a2a77bbb915653aa2bca272ad · 439 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 b87739a577a62459915cb57bf0a5cfd86b818877a30263a839f4a8accc8d882b · 60,348 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 22:25 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.