3,832,688 launches on record
Coverage from 2 Sep 2026
Archive read 13:46 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 11:38 UTC

LOCKIN

Gb1sphs4BVm1b6mY8KJ1jPtMR49xXpGYFjKy1FDdpump 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 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

0.3%of supply taken by the creator in the first block
37outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 17s 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 217 other launches, all of them this same creator's, and this creator has 1,505 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, 12.9% of the launches whose picture we hold carry one only their own creator reused. They are listed under Seen before, further down this page.

1,506launches on record from this creator wallet, this one included, over 8 days
1,086on 27 Oct, its busiest day
78different tickers; the one it used most is LOCKIN, 218 times
27 Oct: 1,08628 Oct: 7729 Oct: 3131 Oct: 288 Nov: 79 Nov: 317 Nov: 2718 Nov: 247
27 OctThis creator wallet's launches per day (UTC)18 Nov
Its most recent other launches (UTC)TickerNameMint
18 Nov, 14:48LOCKIN LOCKIN██████████
18 Nov, 14:47LOCKIN LOCKIN██████████
18 Nov, 14:46LOCKIN LOCKIN██████████
18 Nov, 14:45LOCKIN LOCKIN██████████
18 Nov, 14:44LOCKIN LOCKIN██████████
18 Nov, 14:43LOCKIN LOCKIN██████████
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 17s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-11-18 11:38 UTC
CreatorFwfpy7F2TTvha2p7bG4Zkhgau4tj3oEC95JnFM4nFy4m
Creator took0.3% of supply in the first block
Outside buyers37 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: 13 within the first 30s, 0 in the very same block the token was created in.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 3.3 h ago and it was finished. Checked 2026-11-18 12:08 UTC.
Creator soldyes
Recorded from5HFa8cbQ7CL7aKjJDr2Zr3… slot 470,921,027
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-18 11:38:50 UTC
Slot 470,921,027, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-11-18 11:39:07 UTC +17s
Confirmed against the venue's own completion state.
Highest price seen2026-11-18 11:39:11 UTC +21s
2.800e-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.
Thirty seconds in13 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 pictureOn 212 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.9% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 418 launches from 178 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 →
This documentThe same launch document, byte for byte, as 210 other launches, all of them this same creator's. Across the archive, 12.4% of the launches whose document we hold carry one only their own creator reused. See them →
This creator1,499 earlier launches, 2 confirmed complete on chain. 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 1 other creator wallet, across 2 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 of 2 creator wallets in all. Across the archive, 63.6% 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
NameLOCKIN
Descriptionmy wife thinks I’m crazy or unfaithful
Metadata heldsha256 9204b43e199ea66e6d675ea728b054ab8a36a89c421b558215de8b6a1f87539b · 322 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 d64c540cee49aaff3e1c7e910e0f9b8158847a5bc4b3905436d7282807a0abe0 · 243,572 bytes

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