2,365,800 launches on record
Coverage from 2 Sep 2026
Archive read 05:21 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

MEME

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.

Also recorded, and not part of the finding above: this creator has 3 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. 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.

HC3GbAKiTkGEHsVvaAJ6NmuNmh1WoreqMGPoi3datABj Solscan

Cite this record as: Chain of Title, MEME (Memecoin), mint HC3GbAKiTkGEHsVvaAJ6NmuNmh1WoreqMGPoi3datABj, observed at creation 2026-10-25 01:15 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/HC3GbAKiTkGEHsVvaAJ6NmuNmh1WoreqMGPoi3datABj

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.
noteThe creator took 20.0% of supply at launch.
findingIt left the curve 0s after launch.

At launch

Created2026-10-25 01:15 UTC
CreatorGcFVWBZzrpUV2VU1q5BdLucrqha4eLt4zxamcCR3VxAY
Creator took20.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.
Graduatedin the same batch of events as the 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 from4vg3GAED4oCg1GEPLVxDJM… slot 461,067,160
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.

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-25 01:15:09 UTC
Slot 461,067,160, which is the chain's own clock for this moment.
Curve completed2026-10-25 01:15:09 UTC
Confirmed against the venue's own completion state.

Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.

Seen before

This pictureNo other launch we hold a picture for used this one.
This tickerOn 3,104 launches from 1,936 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.2% wear one that more than one creator wallet has launched. See this ticker's page →
This creator3 earlier launches, 3 confirmed complete on chain. Across the archive, 70.1% 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 7 other creator wallets, across 6 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, 61.2% 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
NameMemecoin
DescriptionPump V1
Metadata heldsha256 b08e9acd3746635775d958bffdb12658eb4fc014b2583ca6f9541196e20cc1b6 · 204 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 cf25e6b0f5ac67582cf1bfa4a4613fdada3cc7349e46fcd51661a1eebc1d76d6 · 316,453 bytes

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