2,146,934 launches on record
Coverage from 2 Sep 2026
Archive read 19 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

A.I.V.A.

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 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, 50.7% 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.

3MZ41SJKAvBcG8RU3QS3oh6pWb4Zi2w6V3U4Q6FLpump Solscan pump.fun

Cite this record as: Chain of Title, A.I.V.A., mint 3MZ41SJKAvBcG8RU3QS3oh6pWb4Zi2w6V3U4Q6FLpump, observed at creation 2026-10-19 17:36 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/3MZ41SJKAvBcG8RU3QS3oh6pWb4Zi2w6V3U4Q6FLpump

At launch

Created2026-10-19 17:36 UTC
CreatorGgAhdLoCiJBuXqYAD84AqBwaC6hZVB8oqZZHSvXoAgDG
Creator took9.8% of supply in the first block
Outside buyers398 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: 151 within the first 30s, 6 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.
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 soldnot while we watched
Recorded fromPWcuX4V72PjbiZoZtbRcYF… slot 458,918,388
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-19 17:36:06 UTC
Slot 458,918,388, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Highest price seen2026-10-19 17:36:06 UTC
0.000e+0 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 in151 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 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 50.7% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 9 launches from 7 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.8% 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, 27.9% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 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, 59.7% 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
NameA.I.V.A.
Metadata heldsha256 03d76c9d1a097c3c0e3df4725c855749d091ca89f2bc324d3e57ef3a0c2470ae · 219 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 1cf9b216ae038febd1dadc2a3229699dfc5e806474ba200fd691789a2db10d4a · 2,807 bytes

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