2,188,691 launches on record
Coverage from 2 Sep 2026
Archive read 19:48 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

PEPITO

The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

59mXodQ31VyP5fj4uz9qsCkhL17k1Ec6irLeqPARpump Solscan pump.fun

Cite this record as: Chain of Title, PEPITO (Pepitocoin), mint 59mXodQ31VyP5fj4uz9qsCkhL17k1Ec6irLeqPARpump, observed at creation 2026-09-03 02:05 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/59mXodQ31VyP5fj4uz9qsCkhL17k1Ec6irLeqPARpump

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 0s after launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-03 02:05 UTC
Creator3WrX3BQCdjkrvzqbKJsXGL7qkrQVrPUgnywPv3gNQgCB
Creator took3.4% 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: 36 within the first 30s, 4 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 40.9 days ago and it was finished. Checked 2026-09-10 00:19 UTC.
Creator soldyes
Recorded from5iYqQpWQsB54XUMBStGzA3… slot 443,852,422
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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.

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-09-03 02:05:28 UTC
Slot 443,852,422, which is the chain's own clock for this moment.
Creation block4 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-09-03 02:05:28 UTC +0s
Confirmed against the venue's own completion state.
Thirty seconds in36 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.
Highest price seen2026-09-03 02:53:26 UTC +47m 58s
2.858e-6 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 26 launches from 25 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, 87.9% wear one that more than one creator wallet has launched. See this ticker's page →

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
NamePepitocoin
Description$PEPITO is Elon’s API cat. He posted every time he left and every time he came home — Elon saw it, replied, and opened a free API so he could stay.
Metadata heldsha256 1b02f2b1e6eb899a8b7c943412997a833df1c3b7b22690933d40977591ed862f
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-09-23 00:20 UTC.
Picture heldsha256 550136ca86fd0f95c36cb4061f8bb772922dac19006f7e634ce12ed295c951b3 · 228,545 bytes

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