Skip to main content

transaction_entry RPC Method

Retrieves information on a single transaction from a specific ledger version

Updated on
Oct 4, 2023

transaction_entry RPC Method

This method does not support retrieving information from the current in-progress ledger. You must specify a ledger version in either ledger_index or ledger_hash.

Parameters

tx_hash
string
The unique hash of the transaction you are looking up
ledger_index
integer
The ledger index of the ledger to use, or a shortcut string to choose a ledger automatically
ledger_hash
integer
A 20-byte hex string for the ledger version to use

Returns

result
object
An object which contains the following fields:
tx_json
object
The tx_json object with the following fields:
Account
string
The unique address of the account that initiated the transaction
Amount
string
The amount of the transaction
Destination
string
The recipient of the transaction
Fee
string
The amount of XRP, in drops, to be destroyed as a cost for distributing this transaction to the network
Flags
integer
The set of bit-flags for this transaction
LastLedgerSequence
integer
The highest ledger index this transaction can appear in
Memos
array
The additional arbitrary information used to identify this transaction
Sequence
integer
The sequence number of the account sending the transaction
SigningPubKey
string
The hex representation of the public key that corresponds to the private key used to sign this transaction
TransactionType
string
The type of transaction. Valid transaction types include: Payment, OfferCreate, TrustSet, and many others
TxnSignature
string
The signature that verifies this transaction as originating from the account it says it is from
hash
string
The hash of the transaction
metadata
object
The metadata object which contain the following fields:
AffectedNodes
array
The AffectedNodes object which contain the following fields:
ModifiedNode
object
The ModifiedNode object which contain the following fields:
FinalFields
object
The content fields of the ledger object after applying any changes from this transaction
Account
string
The account related to the modified node
Balance
string
The balance of the account
Flags
integer
The set of bit-flags for this transaction
OwnerCount
integer
The number of owners for the account
Sequence
integer
The sequence number of the account
LedgerEntryType
string
The type of ledger object that was deleted
LedgerIndex
string
The ID of this ledger object in the ledger's state tree
PreviousFields
object
The previous values for all fields of the object that were changed as a result of this transaction
Balance
string
The previous balance of the account
Sequence
integer
The previous sequence number of the account
PreviousTxnID
string
The identifying hash of the previous transaction to modify this ledger object
PreviousTxnLgrSeq
integer
The Ledger Index of the ledger version containing the previous transaction to modify this ledger object
TransactionIndex
integer
The transaction's position within the ledger that included it
TransactionResult
string
A result code indicating whether the transaction succeeded or how it failed
delivered_amount
string
The currency Amount actually received by the Destination account
ledger_index
integer
The index of the ledger to retrieve information from
ledger_hash
string
The hash of the ledger where the transaction is stored
validated
boolean
It indicates whether the result has been validated
status
string
The status of the request
warnings
array
An array of warning objects, each containing the following fields:
id
integer
The ID of the warning
message
string
The warning message
Request
1
curl https://docs-demo.xrp-mainnet.quiknode.pro/ \
2
  -X POST \
3
  -H "Content-Type: application/json" \
4
  --data '{
5
    "method": "transaction_entry",
6
	"params": [{
7
        "tx_hash": "71A26ED3AD40802121D0C56DAAFA4C7ACC421153312312B701D1B23E8C6E2306",
8
        "ledger_index": 38686567
9
    }],"id":1,"jsonrpc":"2.0"}'
Don't have an account yet?
Create your QuickNode endpoint in seconds and start building
Get started for free