2,926,398 launches on record
Coverage from 2 Sep 2026
Archive read 03:27 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

STENKS

The curve completed 19s 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 2,694 other launches from 734 creator wallets in all. 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, 54% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

3s3D4nn9yMd3qKQDH4BQEgDkmahKWJTtA7QKSwPKpump Solscan pump.fun

Cite this record as: Chain of Title, STENKS, mint 3s3D4nn9yMd3qKQDH4BQEgDkmahKWJTtA7QKSwPKpump, observed at creation 2026-10-29 21:08 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/3s3D4nn9yMd3qKQDH4BQEgDkmahKWJTtA7QKSwPKpump

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 19s after launch.

At launch

Created2026-10-29 21:08 UTC
CreatorHvLEGAUvVpCkCDjvXEF69gGUvm52PzDDXeXaSbMG7d7J
Creator took0.5% of supply in the first block
Outside buyers13 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: 3 within the first 30s, 0 in the very same block the token was created in.
Graduated0 min after launch
Curve on chainIncomplete. We read the bonding curve account 10.0 h ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-10-31 02:12 UTC.
Creator soldnot while we watched
Recorded from2M2QJNVW4tAp5aBXzvpVKQ… slot 463,026,823
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-29 21:08:31 UTC
Slot 463,026,823, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-29 21:08:50 UTC +19s
Confirmed against the venue's own completion state.
Highest price seen2026-10-29 21:08:55 UTC +24s
2.632e-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 in3 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 2,323 launches from 734 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 54% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 2,136 launches from 696 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, 88.4% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 1,797 other launches, across 660 creator wallets in all. Across the archive, 31.1% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

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
NameSTENKS
Metadata heldsha256 c0fc591b62b250197b4f97bf31ebcbbd203281f34b897a79082b3c04213924ce · 191 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 82570e466eec0736c0931820d62938624c6714bf31ac07fcba94d683079a03ec · 206,617 bytes

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