# Inspect data provenance


In the Contributor portal, open **Contributions**, choose a submission, and select **Track record** to open its **Submission Tracker**. Confirm the Campaign and Submission first. **Back to Contributions** returns to the list; **Open in Earnings** opens the separate pay view.

A Developer can start with an authorized **Campaign → Reviews → Review** result, or the identifiers in a delivered record. Record the Campaign and Submission ID there; do not use another person's Contributor Tracker. If that view does not supply a CF or chain link, [ask support](/help/support) to reconcile the platform record with any public record. If you already hold a CF, dataset-version ID, or DID, start directly in Explorer below.

## Read the reported lineage

| Stage | What it records |
| --- | --- |
| Submitted | The submission |
| Validated & accepted | Checks and acceptance |
| Anchored on-chain | A chain anchor |
| Included in dataset | Reported dataset membership |
| Published downstream | A downstream publication record |
| Royalty walked back to you | Related royalty return information |

Not every submission completes every stage. Read each status with its timestamp and explanation. **Completed** means the page reports that stage complete. **Not started** means it has not begun. **Not reported** means this page has no report for that stage. It does not prove the stage failed, that the underlying outcome is impossible, or that its amount is zero; check **Earnings** for what you were paid.

For example, **Next → Complete** in Contributions can mean the submission was accepted and has an award, while **Anchored on-chain** and **Included in dataset** are still **Not started**. Those labels answer different questions. If the same event has conflicting status, time, or reference in two views, keep the Submission ID, both redacted views, and the time checked; [contact support](/help/support) about that original record instead of resubmitting work.

## Cross-check in XnY Explorer

If you have a Contribution Fingerprint (CF), dataset ID, or DID, open [XnY Explorer](https://explorer.xny.ai) and use **Search by id or DID**. For a Contribution, inspect:

1. **Details** for CF ID, author, task or Campaign, frontier, verdict, quality grade, and verifier.
2. **Payload** for metadata hash and URI. **Payload not served here — reference only** is a reference, not an original-file download.
3. **Chain of records** for network, transaction hash, and block. Distinguish mainnet from testnet.
4. **Lineage** for the relationships actually listed. Check whether a CF is a member of the **specific dataset version** you mean; a contribution-to-contribution derivation and a dataset-version derivation are different links.

A CF ID, Humanbased Submission ID, dataset-version ID, and transaction hash identify different things. With only a Submission ID, use the role-appropriate source above to seek a chain association. If none is available, [contact support](/help/support) rather than using the platform ID as a CF ID.

For example, a CF may be listed as a member of dataset version A while version B says it derives from A. The version relationship alone does not show that the same CF is a member of B; check B's membership record. An empty graph is not proof of no source: some derivation depends on declared metadata or a separate [XnY lineage query](https://docs.xny.ai/concepts/products/data-lineage). These records cannot trace every external copy or prove that a model used the data.

Hashes and URIs help associate metadata with content. A matching digest can establish consistency for the referenced bytes; it cannot alone establish a person's real-world identity, content quality, or usage rights. See [access and authorization](/data/rights).