Optional opts: TransactionBlockhashCtorOptional opts: TransactionNonceCtorOptional opts: TransactionCtorFields_DEPRECATEDTransactionCtorFields has been deprecated and will be removed in a future version.
Please supply a TransactionBlockhashCtor instead.
Optional feeThe transaction fee payer
The instructions to atomically execute
Optional lastthe last block chain can advance to before tx is exportd expired
Optional minIf this is a nonce transaction this represents the minimum slot from which to evaluate if the nonce has advanced when attempting to confirm the transaction. This protects against a case where the transaction confirmation logic loads the nonce account from an old slot and assumes the mismatch in nonce value implies that the nonce has been advanced.
Optional nonceOptional Nonce information. If populated, transaction will use a durable Nonce hash instead of a recentBlockhash. Must be populated by the caller
Optional recentA recent transaction id. Must be populated by the caller
Signatures for the transaction. Typically created by invoking the
sign() method
The first (payer) Transaction signature
Add one or more instructions to this Transaction
Rest ...items: (TransactionInstruction | Transaction | TransactionInstructionCtorFields)[]Add an externally created signature to a transaction. The public key must correspond to either the fee payer or a signer account in the transaction instructions.
Get the estimated fee associated with a transaction
Partially sign a transaction with the specified accounts. All accounts must correspond to either the fee payer or a signer account in the transaction instructions.
All the caveats from the sign method apply to partialSign
Rest ...signers: Signer[]Serialize the Transaction in the wire format.
Optional config: SerializeConfigSpecify the public keys which will be used to sign the Transaction. The first signer will be used as the transaction fee payer account.
Signatures can be added with either partialSign or addSignature
Rest ...signers: PublicKey[]Deprecated since v0.84.0. Only the fee payer needs to be
specified and it can be set in the Transaction constructor or with the
feePayer property.
Sign the Transaction with the specified signers. Multiple signatures may be applied to a Transaction. The first signature is considered "primary" and is used identify and confirm transactions.
If the Transaction feePayer is not set, the first signer will be used
as the transaction fee payer account.
Transaction fields should not be modified after the first call to sign,
as doing so may invalidate the signature and cause the Transaction to be
rejected.
The Transaction must be assigned a valid recentBlockhash before invoking this method
Rest ...signers: Signer[]Static fromParse a wire transaction into a Transaction object.
Static populatePopulate Transaction object from message and signatures
Optional signatures: string[]
Transaction class