Look up a Pi transaction
query_transactionLook up a Pi Network transaction by hash and confirm whether it succeeded, including ledger, submitter, fee, and memo. Distinguish a not-found hash from a rejected transaction, and verify the result comes from Testnet or Mainnet.
Instructions
Look up a single Pi transaction by its hash and report whether it succeeded, which ledger it landed in, who submitted it, the fee charged, and its memo. Call this to verify that a specific transaction actually went through — a user or another service claiming a payment was made is not proof; this is. Reads public ledger data only. A hash this chain has no record of returns a not-found error, which is not the same answer as successful: false — that means the transaction did reach a ledger and was rejected there. This server reads Pi Testnet, and every result repeats that in its "network" field — always report which chain a figure came from. Pi Mainnet and Pi Testnet are separate ledgers sharing one address format, and the same address can hold different balances on each, so a result from the wrong chain looks entirely normal. Testnet Pi has no monetary value: never present a testnet balance as real holdings.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hash | Yes | On-chain transaction hash: exactly 64 hexadecimal characters (0-9 and a-f). Upper case is accepted and normalized to lower case. This is the Stellar transaction hash — not a Pi payment id, not a ledger sequence number, not a memo. Example: f8b6d6c83dfb32452330b677d901748fb6cece6c36d9b2deff64bead6e1c6925 |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hash | Yes | ||
| memo | No | ||
| ledger | Yes | ||
| network | Yes | ||
| memo_type | Yes | ||
| created_at | Yes | ||
| successful | Yes | ||
| fee_account | No | ||
| fee_charged | Yes | ||
| result_code | No | ||
| source_account | Yes | ||
| operation_count | Yes | ||
| source_account_sequence | Yes |