📘
Supported on NEAR (mainnet) only.

Parameters

transaction hash - string - The hash of the transaction
sender account id - string - The id of the sender account

Returns

receipts_outcome - The receipts outcome for the transaction
- block_hash - The hash of the block this transaction was associated with
- id - The transaction id
- outcome - The outcome associated with transaction
  - executor_id - The id of the originator
  - gas_burnt - The gas burnt while executing the transaction
  - logs - Logs for the application being executed by this transaction
  - metadata - It describes the transaction information
    - gas_profile - The information about the gas such as gas used, cost and cost_category
      - cost - The cost of the gas used
      - cost_category - The category of the cost
      - gas_used - The amount of gas used
    - version - The version number
  - receipt_ids - The id of the recipients
  - status - The status of the transaction
    - SuccessReceiptId - The transaction id of the successful recipient
  - tokens_burnt - The amount of tokens burnt
- proof - The proof of the transaction
  - hash - The hash of the proof
  - direction - The direction
status - The status of the transaction
- SuccessValue - The value successfully sent
transaction - The transaction object
- actions - An action built from near-api-js.transactions
  - FunctionCall - An action to be performed on the receiver_id
    - args - The transaction specific argument
    - deposit - The amount deposited
    - gas - Integer of the gas provided for the transaction execution
    - method_name - The name of the method corresponding to the actions
  - hash - The transaction hash
  - nonce - The number of transactions made by the sender prior to this one encoded as hexadecimal
  - public_key - The public key of the signer
  - receiver_id - The account id of the transaction receiver
  - signature - The standard ed25519 signature type
  - signer_id - The account id of the transaction originator
transaction_outcome - The transaction outcome for the transaction
- block_hash - The hash of the block this transaction was associated with
- id - The id of the transaction
- outcome - The outcome associated with transaction
  - executor_id - The id of the originator
  - gas_burnt - The gas burnt while executing the transaction
  - logs - Logs for the application being executed by this transaction
  - metadata - It describes the transaction information
    - gas_profile - The information about the gas such as gas used, cost and cost_category
    - version - The version number
  - receipt_ids - The id of the recipients
  - status - The status of the transaction
    - SuccessReceiptId - The transaction id of the successful recipient
  - tokens_burnt - The amount of tokens burnt
- proof - The proof of the transaction
  - hash - The hash of the transaction
  - direction - The direction

API Endpoint

The format of a Near API endpoint is
https://open-platform.nodereal.io/{{apiKey}}/near/

Here is an example:
https://open-platform.nodereal.io/4c0a1c23661a4e26bcbcwed461e34ea9/near/

Example

Request

curl https://open-platform.nodereal.io/{{apiKey}}/near/ \
-X POST \
-H "Content-Type: application/json" \
--data '{"jsonrpc": "2.0", "method": "tx", "params": ["Ce4DPVFyDRdx54iLoSiKA6gqwGnE5V4mTZyVvFDQsvmN","relay.aurora"],"id":1}'

Result