retardutride
Also recorded, and not part of the finding above: this picture is on 9 other launches from 2 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, 54% 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, retardutride, mint 9FNp1YaNvgce2kAVorc35m14eQRoziWXcwcruH9epump, observed at creation 2026-10-29 14:50 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/9FNp1YaNvgce2kAVorc35m14eQRoziWXcwcruH9epump
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-10-29 14:50 UTC |
| Creator | HXTsUm8kkx5qZCyYyfYxb19gsSof8sejUBBFm1nofgxz |
| Creator took | 2.8% of supply in the first block |
| Outside buyers | 523 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: 75 within the first 30s, 18 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 | 6 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 | yes |
| Recorded from | LnsjeAZ6WKoDW4pan1zk9F… slot 462,920,793
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
| Created | 2026-10-29 14:50:10 UTC Slot 462,920,793, which is the chain's own clock for this moment. |
| Creation block | 18 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 75 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-10-29 14:55:59 UTC +5m 49s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-29 14:55:59 UTC +5m 49s
4.109e-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. |
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 4 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 54% of the launches whose picture we hold carry one a different creator also used. See them → |
Pool
| Liquidity | 2.6 SOL |
| Read from chain | 2026-10-29 19:19 UTC, just now |
What this launch claimed to be
| Name | retardutride |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 a8004ff81a5a73d8a5e6192b4c964189f66d0f69aa72b4fd36221e4ceac6bda1 · 475 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 18ae93b70ee7f8b882808965ca0590342d871f21475e55579212b16dcd10f885 · 25,070 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-29 14:50 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.