The unique address of the transaction sender.
OptionalAccountHash value identifying another transaction. If provided, this transaction is only valid if the sending account's previously-sent transaction matches the provided hash.
OptionalFeeInteger amount of XRP, in drops, to be destroyed as a cost for distributing this transaction to the network. Some transaction types have different minimum requirements.
OptionalFlagsSet of bit-flags for this transaction.
OptionalLastHighest ledger index this transaction can appear in. Specifying this field places a strict upper limit on how long the transaction can wait to be validated or rejected.
OptionalMemosAdditional arbitrary information used to identify this transaction.
Identifies the MPTokenIssuance object to be removed by the transaction.
OptionalNetworkIDThe network id of the transaction.
OptionalSequenceThe sequence number of the account sending the transaction. A transaction is only valid if the Sequence number is exactly 1 greater than the previous transaction from the same account. The special case 0 means the transaction is using a Ticket instead.
OptionalSignersArray of objects that represent a multi-signature which authorizes this transaction.
OptionalSigningHex representation of the public key that corresponds to the private key used to sign this transaction. If an empty string, indicates a multi-signature is present in the Signers field instead.
OptionalSourceArbitrary integer used to identify the reason for this payment, or a sender on whose behalf this transaction is made. Conventionally, a refund should specify the initial payment's SourceTag as the refund payment's DestinationTag.
OptionalTicketThe sequence number of the ticket to use in place of a Sequence number. If this is provided, Sequence must be 0. Cannot be used with AccountTxnID.
The type of transaction. Valid types include: Payment, OfferCreate,
TrustSet, and many others.
OptionalTxnThe signature that verifies this transaction as originating from the account it says it is from.
The MPTokenIssuanceDestroy transaction is used to remove an MPTokenIssuance object from the directory node in which it is being held, effectively removing the token from the ledger. If this operation succeeds, the corresponding MPTokenIssuance is removed and the owner’s reserve requirement is reduced by one. This operation must fail if there are any holders who have non-zero balances.