Skip to main content
Retrieves information on a single transaction from a specific ledger version. The tx method, by contrast, searches the whole available history (ledger 32,570 onward) for the specified transaction and is usually the better choice. This method will use 20 Compute Units.

Reference: Here

Parameters

  • tx_hash (string, required) Unique hash of the transaction you are looking up.
  • ledger_hash (string, optional) The unique hash of the ledger version to use.
  • ledger_index (string or unsigned integer, optional) The ledger index of the ledger to use. The transaction must be in this exact ledger, so pass the ledger that contains it rather than a shortcut such as validated.

Returns

  • ledger_index (number) The ledger index of the ledger version the transaction was found in.
  • ledger_hash (string) The identifying hash of the ledger version the transaction was found in.
  • metadata (object) The transaction metadata, which shows the exact results of the transaction in detail.
  • tx_json (object) JSON representation of the transaction.
  • validated (boolean) If true, the transaction is in a validated ledger.
Over WebSocket, send {"id":1,"command":"transaction_entry","tx_hash":"EAF2C49070D83BB7A6DFC4DAF2547E01BA69248B9C4E9DE429BCF7406F6B250E","ledger_index":107045822} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.