3,413,750 launches on record
Coverage from 2 Sep 2026
Archive read 06:58 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

CHILLCAT

The creator took 35% of supply at 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 3 other launches from 3 creator wallets in all, and this creator has 10 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, 55.9% 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.

He7pvZk3JUTGnvLeHpXKviVapedZfeU7BFZ3NWCSpump Solscan pump.fun

Cite this record as: Chain of Title, CHILLCAT (Just a chill cat), mint He7pvZk3JUTGnvLeHpXKviVapedZfeU7BFZ3NWCSpump, observed at creation 2026-09-03 18:54 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/He7pvZk3JUTGnvLeHpXKviVapedZfeU7BFZ3NWCSpump

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.

noteThe creator took 35.4% of supply at launch.
noteThe creator sold while we were watching.

At launch

Created2026-09-03 18:54 UTC
Creator7JGBp3vGHgZRibo8YhBUQnKdqN1UqzY2czs8DBgdU31n
Creator took35.4% of supply in the first block
Outside buyers20 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: 1 within the first 30s, 0 in the very same block the token was created in.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldyes
Recorded from4RG87uWqC1e4MTZ28SC96E… slot 444,044,686
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-09-03 18:54:37 UTC
Slot 444,044,686, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in1 distinct buyer, 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 18:59:03 UTC +4m 26s
7.094e-8 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 pictureOn 4 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 152 launches from 119 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.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 2 other launches, across 3 creator wallets in all. Across the archive, 32.8% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator10 earlier launches, none of which reached a graduation threshold while we watched. 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 7 other creator wallets, across 17 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.8% 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
NameJust a chill cat
Metadata heldsha256 b181eb1fd60f31397bad03136161183ccc8fd7dbc0522d9cf038add73ec87231 · 189 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 a82ab13bc1b08f21ef05f18ded166baf26e85569ad7d0a1396e70293625c3c41 · 24,246 bytes

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