See exactly what happened, and show anyone
PaxScan turns a transaction hash into a page that a finance lead, a developer and a customer can all read, and that none of them has to take on faith.
It is the shared record for everyone who uses the network. When a payment is questioned, you send a link, not a screenshot.
A dispute between an agent and a provider usually ends in two logs that disagree. On Paxeer X it ends in a URL. Paste a transaction hash into PaxScan and you see what was sent, to whom, for how much, whether it succeeded, who paid the fee, and the network's own signature over all of it. The provider sees the same page. So does your accountant.
Because every native feature, from budgets to perpetuals to bridge deposits, is an ordinary transaction, each shows up here with the same clarity. There is no second dashboard for the agent side of the network.
What a transaction page tells you
- The result: success, or a revert with a plain reason such as a budget exceeded or a counterparty not allowed.
- The status, one of three: submitted, receipted or committed. Committed means final, with nothing after it.
- The network's signature over the receipt, so you can confirm the page matches what the sender was told at the moment of sending.
- The transaction's exact position in the global order, which is what makes two receipts comparable.
- The fee, the coin it was paid in, and whether an app sponsored it so the user saw nothing.
- Decoded events: a grant drawn, a stream started, a position opened, a token launched, a deposit credited.
Ask the customer for the hash, not the story. The page answers most tickets before anyone opens an internal tool.
One page per account
An address page joins the things other explorers keep apart: the EVM address, the agent identity bound to it and the owner that identity answers to, beside balances in PAX, SID and every token, including the sub-accounts an agent uses for margin or a particular service. For an operator running twenty agents, that is one bookmark per agent and a complete picture on each.
History is paged in the order the network committed it, so your export matches your counterparty's, line for line.
Who uses it for what
| Reader | What they open PaxScan for |
|---|---|
| Finance lead | Confirm a payment is final before releasing goods, and export the month's activity with receipts attached |
| Developer | Read the revert reason, inspect decoded events, verify a contract's source |
| Agent operator | Watch each agent's spend against its budget and spot an unexpected counterparty |
| Trader | Check a fill, a funding payment or a liquidation against the market's own events |
| Counterparty | Verify a payment they were promised, without an account or a login |
The explorer is not our view of the chain. It is the chain's view of itself, rendered.
Run your own copy
PaxScan is open source. Point it at any node, including one you run, and you have an explorer no one else can edit, cache or take down. Teams with compliance requirements run it inside their own network and link to it from internal tools. Everything on paxscan.io, including contract verification and decoded events, works the same way on your instance.
Related
Turn a receipt into evidence
Statements and exports carry the same signed receipts PaxScan shows, ready for an auditor who never visits the site.