Preliminary report · preview, read 2026-11-15 07:04:05 UTC
10 launches from this wallet. 5 other wallets launched with the identical files.
9z5V5PGoaruodVumTnMoU7dsRWn6TAVFzoNDLJTTvbBx
On its own, a launch reads as one launch. This is what the record ties to the wallet behind it.
Every count here is real, and free. Which wallets, which launches and which files: each is struck out like this ██████████ until you open the report.
Preliminary report
9z5V…vbBx
What the record ties to it.
Wallets that launched with the same files
5 other creator wallets launched with a file byte-identical to one this wallet launched with. The 5 listed have 75 launches on record between them. Most shared files first.
| Other wallet | Kinds of file | Files shared | Its launches | First launch | Latest launch | |
|---|---|---|---|---|---|---|
| 1 | ██████████ | 2 | 2 | 71 | 2026-11-13 | 2026-11-15 |
| 2 | ██████████ | 2 | 2 | 1 | 2026-11-14 | 2026-11-14 |
| 3 | ██████████ | 2 | 2 | 1 | 2026-11-14 | 2026-11-14 |
| 4 | ██████████ | 2 | 2 | 1 | 2026-11-14 | 2026-11-14 |
| 5 | ██████████ | 2 | 2 | 1 | 2026-11-14 | 2026-11-14 |
An independent reuse is a separate occasion on which the two wallets carried the same file: several shared files riding one pair of launches count once. "Not read" is a figure this document did not read, never a zero.
The files they share
5 files shared between this wallet and those wallets, the ones carried by the most of them first. A picture and a launch document are matched by the sha256 of their bytes.
| Kind | File | Paired wallets carrying it | Launches on record carrying it | Creator wallets on record carrying it |
|---|---|---|---|---|
| Picture | ██████████ | 3 | 5 | 5 |
| Ticker and name | ██████████ | 3 | ||
| Picture | ██████████ | 2 | 4 | 4 |
| Launch document | ██████████ | 1 | 2 | 2 |
| Launch document | ██████████ | 1 | 7 | 5 |
The group
The chain of shared files leading out from this wallet passes the size at which this register states a group, so none is stated. A chain that long usually runs through a file many unrelated wallets used. The direct pairings above are unaffected: each one is this wallet and one other, and the files they share.
This wallet's launches
10 launches, the first on 2026-11-14 and the most recent on 2026-11-14, on 1 separate day. Its busiest day was 2026-11-14, with 10. It has used 9 tickers, one of them 2 times.
| Launched | Ticker | Name | Mint |
|---|---|---|---|
| 2026-11-14 22:02:47 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-14 21:50:12 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-14 21:01:02 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-14 20:45:45 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-14 20:24:03 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-14 20:03:18 UTC | ██████████ | ██████████ | ██████████ |
| 4 more launches in the report. | |||
What this is, and what a signed report adds
- This is the register's own output, read at the moment above. It carries no signature, no custodian declaration and no addressee.
- It states what was recorded. A shared file establishes that the same file was used; who used it is the next step, and the wallets listed here are where it starts.
- It covers the launches this register holds, which is not every launch on chain.
- A provenance report ($7,500) is scoped in writing to your matter and adds: the custody of each file from capture to the page, the per-launch ledger with the transaction behind every figure, the funding of the wallets traced hop by hop, and a custodian declaration executed on request.
Open this report
Everything above with the wallets, the launches and the file hashes in it: 5 paired wallets, 5 shared files and 10 launches from this wallet, each by its address. Frozen at the moment you buy it, at a permanent link, with a clean PDF from the page.
One payment, by card, no account. The link arrives by email and is permanent. If you go on to a signed provenance report on this matter, the $750 comes off its $7,500.
Chain Of Title LLC. The method is published at https://chainoftitle.org/method and does not vary by customer; corrections are at https://chainoftitle.org/corrections.