2,178,313 launches on record
Coverage from 2 Sep 2026
Archive read 16:49 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

T-006

The curve completed 5s 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 other launches, all of them this same creator's, and this creator has 323 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.

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.

4Lzc2YGpU4ZbeRdWH68JRtpdtRFSwSD6dq8ctKu2pump Solscan pump.fun

Cite this record as: Chain of Title, T-006 (Unit T-006), mint 4Lzc2YGpU4ZbeRdWH68JRtpdtRFSwSD6dq8ctKu2pump, observed at creation 2026-10-20 13:50 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/4Lzc2YGpU4ZbeRdWH68JRtpdtRFSwSD6dq8ctKu2pump

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

At launch

Created2026-10-20 13:50 UTC
Creator92rjsyV1bKBwW5e4ikXucq6gNCisKYPf9xHYpoJJTKU4
Creator took0.2% of supply in the first block
Outside buyers24 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: 6 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 6.7 h ago and it was finished. Checked 2026-10-20 14:10 UTC.
Creator soldyes
Recorded from62T2VTUnnNSmm7nxHdETJk… slot 459,252,846
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-20 13:50:44 UTC
Slot 459,252,846, 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-20 13:50:49 UTC +5s
Confirmed against the venue's own completion state.
Highest price seen2026-10-20 13:50:49 UTC +5s
1.183e-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 in6 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 3 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 creator323 earlier launches, 4 confirmed complete on chain. Across the archive, 70% 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 4 other creator wallets, across 25 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, 60.1% 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
NameUnit T-006
Metadata heldsha256 be30d248f527a970bf045db91c60f442de7240427adceeb0a1eb93b543a730ff · 193 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 fb752324e3f851559e36ca3935e9360853a363f08aace55eba038b890aeb5cdd · 98,705 bytes

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