Verifying Transactions On-Chain
The protocol settles in USDC on Base, an EVM Layer 2. Every order and settlement is recorded on-chain, so you can confirm any transaction yourself using BaseScan, the public block explorer at basescan.org. BaseScan lets you view the transactions for an address, check token balances, and see whether a transaction succeeded along with its details.
Find your address first. In the app, open My Account or Wallet and copy the address, which starts with 0x.
To look up an address, paste it into the BaseScan search bar and press Enter. The address page lists the ETH balance, the ERC-20 tokens held, and the full transaction history, including token transfers and internal contract calls.
To look up a single transaction, you need its transaction hash, a unique identifier that looks like 0x followed by 64 hexadecimal characters. You can copy the hash from your in-app transaction history or from any row on your BaseScan address page. Paste the hash into the BaseScan search bar and press Enter.
The transaction page shows the fields that matter for verification.
| Field | Meaning |
|---|---|
| Status | Success or Failed |
| Block | The block number where the transaction confirmed |
| Timestamp | The date and time of the transaction |
| From | The address that sent the transaction |
| To | The address or contract that received it |
| Transaction Fee | The gas cost paid |
When a transaction moves a token such as USDC, scroll to the token-transfer section to see the token, the amount, and the sending and receiving addresses. To confirm you are looking at the correct token, open the token and check its contract address against the official one. The canonical USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Base uses chain ID 8453.
If a transaction does not appear, give it a few minutes to confirm and make sure you are searching on Base. If you sent funds and the recipient reports nothing arrived, look up the hash, confirm the status is Success, and check the To address and the token transfer. Keep the hashes for large transactions, since they help support and dispute tickets.