3,882,152 launches on record
Coverage from 2 Sep 2026
Archive read 09:58 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-18 21:00 UTC

DCTY

DacityCoin

B2gVmzatqTDC2cxL6NRGVWd9nfbBRnJPdteXQVsKDc4t Solscan

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

75.0%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
The creator took 75% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
findingThe creator bought its own bonding curve - 71 SOL, from the same wallet that created the token.
findingThe creator took 75.0% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
findingThat purchase is what completed the curve: the token left the curve on the creator's own money.
noteTook 1 bonding curve outright. 141 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-18 21:00 UTC
CreatorHKqKMgQF1efwx5gFhGwP62zRhPnt7cfeTugQJ3GicJGd
Creator took75.0% of supply in the first block
Outside buyersunknown 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.
Graduated4 min after launch
Curve on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot recorded - this venue's trades do not name the wallet
Recorded from5o1VKw3d19eYqt3sRgHQcM… slot 471,076,990
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_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-18 21:00:04 UTC
Slot 471,076,990, which is the chain's own clock for this moment.
Curve completed2026-11-18 21:04:02 UTC +3m 58s
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 1,385 launches from 782 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.8% wear one that more than one creator wallet has launched. See this ticker's page →

Who took the curve

One transaction bought 71 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

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
NameDacityCoin
DescriptionDacityCoin was launched on StonkFun.
Metadata heldsha256 e38505bbe36e4dd9fd9536af95d33f5871eb671ba1b3b2ec7e2d787b8be9122e · 592 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 455b8de82111aabd0b77b5c1d5199814b4c977d1ea2d86c03f1dcc8e80458ae2 · 17,938 bytes

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