Skip to main content

The Transaction Object

When Horizon returns information about a transaction, it uses the following format:

  • ATTRIBUTEDATA TYPE

    DESCRIPTION

  • idstring

    A unique identifier for this transaction.

  • paging_tokennumber

    A cursor value for use in pagination.

  • successfulboolean

    Indicates if this transaction was successful or not.

  • hashstring

    A hex-encoded SHA-256 hash of this transaction’s XDR-encoded form.

  • ledgernumber

    The sequence number of the ledger that this transaction was included in.

  • created_atISO8601 string

    The date this transaction was created.

  • source_accountstring

    The account that originates the transaction.

  • source_account_sequencestring

    The source account's sequence number that this transaction consumed.

  • fee_chargednumber

    The fee (in stroops) paid by the source account to apply this transaction to the ledger.

  • max_feenumber

    The maximum fee (in stroops) that the source account was willing to pay.

  • operation_countnumber

    The number of operations contained within this transaction.

  • envelope_xdrstring

    A base64 encoded string of the raw TransactionEnvelope XDR struct for this transaction.

  • result_xdrstring

    A base64 encoded string of the raw TransactionResult XDR struct for this transaction.

  • result_meta_xdrstring

    A base64 encoded string of the raw TransactionMeta XDR struct for this transaction

  • fee_meta_xdrstring

    A base64 encoded string of the raw LedgerEntryChanges XDR struct produced by taking fees for this transaction.

  • memostring

    The optional memo attached to a transaction.

  • memo_typestring

    The type of memo. Potential values include MEMO_TEXT, MEMO_ID, MEMO_HASH, MEMO_RETURN.

  • signaturesstring

    An array of signatures used to sign this transaction.

  • valid_afterRFC3339 date-time string

    The date after which a transaction is valid. This field is deprecated in lieu of preconditions.time_bounds.min_time and will be removed in Horizon v3.

  • valid_beforeRFC3339 date-time string

    The date before which a transaction is valid. This field is deprecated in lieu of preconditions.time_bounds.max_time and will be removed in Horizon v3.

  • preconditionsobject

    A set of transaction preconditions affecting its validity.

    Show child attributes
    • time_boundsobject

      The time range for which this transaction is valid, with bounds as unsigned 64-bit UNIX timestamps

      Show child attributes
      • min_timestring

        the lower bound

      • max_timestring

        the upper bound

    • ledger_boundsobject

      The ledger range for which this transaction is valid, as unsigned 32-bit integers.

      Show child attributes
      • min_ledgernumber

        the lower bound

      • max_ledgernumber

        the upper bound

    • min_account_sequencestring

      Containing a positive, signed 64-bit integer representing the lowest source account sequence number for which the transaction is valid.

    • min_account_sequence_agenumber

      The minimum duration of time (in seconds as an unsigned 64-bit integer) that must have passed since the source account's sequence number changed for the transaction to be valid.

    • min_account_sequence_ledger_gapnumber

      An unsigned 32-bit integer representing the minimum number of ledgers that must have closed since the source account's sequence number changed for the transaction to be valid.

    • extra_signersarray of strings

      The list of up to two additional signers that must have corresponding signatures for this transaction to be valid.