Transaction
The effects of executing a transaction.
Properties
Auxiliary data that are not protocol-critical, generated as part of the effects but are stored separately. Storing it separately allows us to avoid bloating the effects with data that are not critical. It also provides more flexibility on the format and type of the data.
Objects whose state are changed by this transaction.
The set of transaction digests this transaction depends on.
The digest of the events emitted during execution, can be None if the transaction does not emit any event.
Information about the gas object. Also present in the changed_objects vector.
The gas used by this transaction.
The version number of all the written objects (excluding packages) by this transaction.
Returns the field-presence view for this TransactionEffects instance.
The status of the execution.
The transaction digest.
Consensus objects that are not mutated in this transaction. Unlike owned objects, read-only consensus objects' version are not committed in the transaction, and in order for a node to catch up and execute it without consensus sequencing, the version needs to be committed in the effects.