Read revenue receipts and snapshots

Discovery and evidence · Reference · Public, partial and unaudited platform-recorded evidence. Environment and coverage labels matter.

Inspect recorded native-asset receipts, coverage and exports without treating them as profit or spendable balances.

Reviewed: 2026-10-18

Before you start

  • No account is needed for the public ledger.
  • A successfully loaded snapshot for filters, receipt detail and export.

Partial records are not complete business accounting

The Revenue page counts only fees the platform has recorded. Missing rows mean no record was included, not proof that nothing was earned. Read coverage notices and whether the snapshot describes production or development records.

Revenue is collected fees less the shown shares/refunds before operating expenses; it is not net business profit, a wallet balance or a user entitlement. A ledger total does not establish that all funds are presently spendable.

  1. Open /revenue and read the coverage and environment notice before comparing figures.
  2. Expand the detailed ledger and inspect receipts and methodology for the metric you need.
  3. Follow the relevant transaction/reference evidence rather than using an aggregate as proof of a particular payment.

Keep a comparison on one snapshot

A snapshot provides a stable view for paging and filtering while newer data may arrive. Inspect its capture time and ID. Failed refreshes can leave an explicitly stale last-good snapshot on screen.

Snapshots expire and do not survive a server restart. Use Take a new snapshot when expired, or Refresh snapshot for a new view. A bounded auto-refresh control does not guarantee permanent freshness. Do not compare pages from different snapshots as though they were one immutable ledger.

  1. Check the visible snapshot time and stale/expired labels.
  2. Page through the same snapshot for a consistent read.
  3. If expired or refresh failed, use the displayed new-snapshot or Retry action and recheck the time before drawing a current conclusion.

Apply filters and export the intended scope

The detailed ledger supports search, native asset, stream, project/unassigned and UTC date bounds. Apply makes the selected scope explicit; Clear or Show everything removes it. Invalid dates, reversed ranges and rejected filters are errors, not an empty verified dataset.

Export JSON is a machine-readable record of the selected snapshot/query scope, not an audited statement or a substitute for chain receipts. Check active filters and snapshot identity before exporting. An export error means no successful export should be assumed.

  1. Expand the detailed ledger and enter the intended filters, with UTC date bounds when needed.
  2. Select Apply and check the active scope and results. Use Clear if the filter is invalid or unexpectedly restrictive.
  3. Inspect receipt details and page through results as needed.
  4. Select Export JSON and verify the file’s snapshot/scope before using it. Retry a failed read/export only; it does not authorize a payment.

Keep asset amounts and allocations distinct

Native-asset totals preserve units; SOL, USDC and unsupported assets must not be blindly summed into one amount. Current USD estimates are separate valuations, not historical conversion proof. Missing historical values are unavailable, not $0.

Gross receipts, creator shares, refunds, retained revenue and platform-burn allocations are different accounting rows. Do not double count them. Pending buyback/burn allocation is not an executed buy or burn; inspect the linked actual transaction evidence for that outcome.