3,629,590 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-10 11:18 UTC

$DICKCOIN

Dick

BJKtb3v5KqC5XWJ9v7gUngDEwjoJu8gwrHCAbk2vpump 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

0.2%of supply taken by the creator in the first block
27outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 30s after 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 71 other launches from 2 creator wallets in all, and this creator has 733 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. 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.

734launches on record from this creator wallet, this one included, over 5 days
333on 10 Nov, its busiest day
83different tickers; the one it used most is $DACITY, 137 times
10 Nov: 33311 Nov: 14112 Nov: 3413 Nov: 12114 Nov: 105
10 NovThis creator wallet's launches per day (UTC)14 Nov
Its most recent other launches (UTC)TickerNameMint
14 Nov, 14:18$Mask Mask██████████
14 Nov, 14:17$DACITY DACITYCOIN██████████
14 Nov, 14:08$LUCIA LUCIA██████████
14 Nov, 14:07$DICKCOIN DickCoin██████████
14 Nov, 14:07PepeTide PepeTide██████████
14 Nov, 14:07PepeTide PepeTide██████████
See all of this creator's launches →

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.

findingIt left the curve 30s after launch.

At launch

Created2026-11-10 11:18 UTC
Creator2yTHjas8wBiSCvMmv1VU3M96nVnVwJN597gA1tz7GMY9
Creator took0.2% of supply in the first block
Outside buyers27 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: 6 within the first 30s, 0 in the very same block the token was created in.
Graduated1 min after launch
Curve on chainComplete. We read the bonding curve account 3.9 days ago and it was finished. Checked 2026-11-10 17:33 UTC.
Creator soldnot while we watched
Recorded from7P18hj1EFx6UXK5UftDC9v… slot 467,700,926
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-10 11:18:24 UTC
Slot 467,700,926, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in6 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.
Curve completed2026-11-10 11:18:54 UTC +30s
Confirmed against the venue's own completion state.
Highest price seen2026-11-10 11:21:22 UTC +2m 58s
1.045e-6 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.

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 72 launches from 2 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 65 launches from 3 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 documentThe same launch document, byte for byte, as 19 other launches, all of them this same creator's. Across the archive, 12.1% of the launches whose document we hold carry one only their own creator reused. See them →
This creator731 earlier launches, 1 confirmed complete on chain, 8 with findings on record. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 13 other creator wallets, across 21 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

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
NameDick
DescriptionMissed out on Pussy well here’s Dick let’s ride this shit to the moon
Metadata heldsha256 94b5b7221ac8132050137df0199232d8e5c6f6f5cdcd31ccc720d5f01dc2ab57 · 264 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-11-11 11:18 UTC.
Picture heldsha256 f36b5f77b633770e81acba7cbda621d0329cbfa038cf4409aaaba735f3c131e7 · 45,172 bytes

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