tx
Retrieves information on a single transaction, by its identifying hash or its CTID. Served from Clio with full public history, so any transaction validated in ledger 32,570 or later can be looked up.
This method will use 20 Compute Units.
Reference: Here
Parameters
transaction(string, optional) The 256-bit hash of the transaction to look up, as hexadecimal. Provide this orctid.ctid(string, optional) The compact transaction identifier of the transaction to look up. Must use uppercase hexadecimal only.binary(boolean, optional) Iftrue, return transaction data and metadata as binary serialized to hexadecimal strings. The default isfalse.min_ledger(number, optional) Use withmax_ledgerto specify a range of up to 1000 ledger indexes, starting with this ledger (inclusive).max_ledger(number, optional) Use withmin_ledgerto specify a range of up to 1000 ledger indexes, ending with this ledger (inclusive).
Returns
hash(string) The unique identifying hash of the transaction.ctid(string) The transaction's compact transaction identifier.date(number) The close time of the ledger in which the transaction was applied, in seconds since the Ripple Epoch.ledger_index(number) The ledger index of the ledger that includes this transaction.inLedgeris a deprecated alias.meta(object or string) Transaction metadata describing the results of the transaction (hex string in binary mode).validated(boolean) Iftrue, this data comes from a validated ledger version.Various transaction fields (
Account,TransactionType,Fee,Sequence,SigningPubKey,TxnSignatureand the type-specific fields) at the top level ofresult, ortx(hex string) in binary mode.searched_all(boolean) Only in a not-found response whenmin_ledgerandmax_ledgerwere provided. Iftrue, all of the specified ledgers were searched.
Over WebSocket, send {"id":1,"command":"tx","transaction":"EAF2C49070D83BB7A6DFC4DAF2547E01BA69248B9C4E9DE429BCF7406F6B250E","binary":false} to wss://mainnet.xrpl.validationcloud.io/v1/<YOUR_API_KEY_HERE>.
Last updated
Was this helpful?