3,625,592 launches on record
Coverage from 2 Sep 2026
Archive read 13:17 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-14 07:46 UTC

VTC

VICE 6

EGf9GvpRuqTrLU3XUENWSEnVqTieaJof7jpcd3uvpump 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 five lists, or with Brand Protection at $79 a month for every list on every record. 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

79.3%of supply taken by the creator in the first block
0outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The creator took 79% of supply at 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 3 other launches, all of them this same creator's. 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.

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.

findingThe creator bought its own bonding curve - 85 SOL, from the same wallet that created the token.
findingThe creator took 79.3% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
noteTook 1 bonding curve outright. 170 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-14 07:46 UTC
CreatorGSDGWpJCfvz6myHsfnwVBbhP2gK5Hn8gcfj6utTUP3xb
Creator took79.3% of supply in the first block
Outside buyers0 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: 0 within the first 30s, 0 in the very same block the token was created in.
Graduatedyes; we did not record when
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 soldnot while we watched
Recorded from57X9n2zbTbowQM7TodVieK… slot 469,249,164
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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

Created2026-11-14 07:46:22 UTC
Slot 469,249,164, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds inNo buyer, 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.
Curve completedRecorded as complete; we did not record when.
Confirmed: a PumpSwap pool was found for it.

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 pictureNo other launch we hold a picture for used this one.
This tickerOn 22 launches from 13 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 →

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

Liquidity1683.2 SOL
Read from chain2026-11-14 13:56 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameVICE 6
DescriptionVice VI | November 19
Metadata heldsha256 ccb1dc48b6dc4e939867f3c10431a77520ec451e4f1cd7e922969b8a1a532612 · 285 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 70d1aaa4ed04e758884459e55670e52d48135da86c5966a2c15ba44677105b9a · 439,930 bytes

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