Clarity, not claims.

One hash is enough.

Copy a transaction hash from your wallet or the Arc Testnet explorer. It begins with 0x and contains 64 hexadecimal characters after that prefix. Paste it into the receipt desk and choose Verify transaction.

TRACEPAY reads the chain ID, transaction, execution receipt, and corresponding block through a fixed public RPC endpoint. It does not request your wallet, private keys, or a signature.

Four states. No ambiguity.

Confirmed execution

The RPC reports a mined receipt with successful execution. Transaction and block references are cross-checked. This does not certify a particular invoice was paid.

Reverted transaction

The transaction was mined, but execution failed. Native value is shown as zero executed value. Gas can still have been spent.

Pending / unavailable receipt

The transaction exists, but the RPC has no receipt yet. No completed receipt export is offered. Try again later.

Not found

No transaction or receipt was returned for this hash on Arc Testnet. A hash from another network will not work here.

If the RPC times out, is unavailable, reports the wrong chain, or returns inconsistent data, verification fails closed. No invented receipt replaces it.

One USDC. Two interfaces.

Arc uses USDC as its native asset. Native transaction values and execution fees use 18 decimals. The official USDC ERC-20 interface at 0x3600000000000000000000000000000000000000 uses 6 decimals.

We use integer arithmetic, not floating-point estimates. The receipt keeps top-level native value separate from Transfer events emitted by that specific contract. These views may describe related movements: they are not added into a total.

Contract calls, minting, burning, and multi-hop activity can produce events. An event is not automatically a payment. Other tokens are not labeled USDC, and internal native transfers are not traced. The transaction recipient can be a contract, not the final beneficiary.

Take your record with you.

Download JSON saves the observed fields, source RPC, chain ID, observation time, limitations, and an integrity fingerprint. Print / PDF opens your browser’s print dialog with a document-only layout; select “Save as PDF” if your browser supports it.

The SHA-256 fingerprint covers only the exported receipt object, serialized as compact JSON with object keys sorted recursively and array order preserved. The integrity envelope is excluded. Recompute using that same serialization to detect changes.

A matching fingerprint proves the file matches its checksum—not that the RPC is correct, that TRACEPAY signed it, or that an external obligation was fulfilled. Looking up again creates a new observation time and therefore a new fingerprint.

Evidence with boundaries.

TRACEPAY is an independent read-only utility, not a wallet, payment processor, tax service, auditor, or consensus client. It trusts the configured public RPC and does not independently verify block consensus. A receipt is not a signed attestation.

Addresses do not prove identity. Transaction success does not prove offchain delivery, invoice fulfillment, legality, or ownership. This version only supports Arc Testnet; test assets have no monetary value.

No receipt history or account database is maintained by the app. Your lookup is sent to our hosting server and the public RPC provider, which may keep standard request logs. Downloaded files are yours to manage. No wallet tracking or analytics script is included.

The network, explicitly.

Network

Arc Testnet

Chain ID

5042002

RPC

https://rpc.testnet.arc.io

Explorer

explorer.testnet.arc.io ↗

Official references used for network configuration and precision:

• Arc · Connect to Arc
• Arc · Contract addresses
• Arc · Stablecoin native model

Arc’s official documentation also lists mainnet. TRACEPAY deliberately supports Testnet only in this release; mainnet hashes are not queried.