Skip to main content
Transaction meta result_meta_xdr will be removed from the SDF hosted Horizon API (horizon.stellar.org) in Q3 2024. Instead of using Horizon to access transaction metadata, developers could access it with the getTransactions endpoint in the Stellar RPC.
When Horizon returns information about a transaction, it uses the following format:
string
A unique identifier for this transaction.
number
A cursor value for use in pagination.
boolean
Indicates if this transaction was successful or not.
string
A hex-encoded SHA-256 hash of this transaction’s XDR-encoded form.
number
The sequence number of the ledger that this transaction was included in.
ISO8601 string
The date this transaction was created.
string
The account that originates the transaction.
string
The source account’s sequence number that this transaction consumed.
number
The fee (in stroops) paid by the source account to apply this transaction to the ledger.
number
The maximum fee (in stroops) that the source account was willing to pay.
number
The number of operations contained within this transaction.
string
A base64 encoded string of the raw TransactionEnvelope XDR struct for this transaction.
string
A base64 encoded string of the raw TransactionResult XDR struct for this transaction.
string
[To be deprecated in Q3] A base64 encoded string of the raw TransactionMeta XDR struct for this transaction
string
A base64 encoded string of the raw LedgerEntryChanges XDR struct produced by taking fees for this transaction.
string
The optional memo attached to a transaction.
string
The type of memo. Potential values include MEMO_TEXT, MEMO_ID, MEMO_HASH, MEMO_RETURN.
string
An array of signatures used to sign this transaction.
object
A set of transaction preconditions affecting its validity.
Example