wank
Also recorded, and not part of the finding above: this picture is on 28 other launches from 22 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, 55.6% 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.
Cite this record as: Chain of Title, wank, mint C3zM2dRJ6x8py4dTqspLiwJTQKAqH5tsKEYjMda2pump, observed at creation 2026-11-06 02:49 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/C3zM2dRJ6x8py4dTqspLiwJTQKAqH5tsKEYjMda2pump
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.
At launch
| Created | 2026-11-06 02:49 UTC |
| Creator | 7g4TisteMahT8dHpMvQuFNf72C19V2ofDPR8MMWmgkUp |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 240 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: 126 within the first 30s, 10 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. |
| Graduated | 1 min after launch |
| Curve on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 4kQSDVEgLGrrT1W8GHRXB9… slot 465,947,108
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | 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
| Created | 2026-11-06 02:49:56 UTC Slot 465,947,108, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 126 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. |
| Curve completed | 2026-11-06 02:51:11 UTC +1m 15s Confirmed: a PumpSwap pool was found for it. |
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 picture | On 29 launches from 22 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55.6% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 83 launches from 48 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.3% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 2 other launches, across 3 creator wallets in all. Across the archive, 32.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
Pool
| Liquidity | 2.8 SOL |
| Read from chain | 2026-11-07 11:12 UTC, just now |
What this launch claimed to be
| Name | wank |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 dd3ad83a2b25ab4751edfb67768b40645408088c22256311e2f7c3be2bb24436 · 288 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 held | sha256 a591a387c0ed54958f3ad1d4be46ac73d59951968a529a8df53d263fd1c12164 · 12,152 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-06 02:49 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.