TxResponse defines a structure containing relevant tx data and metadata. The tags are stringified and the log is JSON decoded.

interface TxResponseAmino {
    code?: number;
    codespace?: string;
    data?: string;
    events?: EventAmino[];
    gas_used?: string;
    gas_wanted?: string;
    height?: string;
    info?: string;
    logs?: ABCIMessageLogAmino[];
    raw_log?: string;
    timestamp?: string;
    tx?: AnyAmino;
    txhash?: string;
}

Properties

code?: number

Response code.

codespace?: string

Namespace for the Code

data?: string

Result bytes, if any.

events?: EventAmino[]

Events defines all the events emitted by processing a transaction. Note, these events include those emitted by processing all the messages and those emitted from the ante handler. Whereas Logs contains the events, with additional metadata, emitted only by processing the messages.

Since: cosmos-sdk 0.42.11, 0.44.5, 0.45

gas_used?: string

Amount of gas consumed by transaction.

gas_wanted?: string

Amount of gas requested for transaction.

height?: string

The block height

info?: string

Additional information. May be non-deterministic.

The output of the application's logger (typed). May be non-deterministic.

raw_log?: string

The output of the application's logger (raw string). May be non-deterministic.

timestamp?: string

Time of the previous block. For heights > 1, it's the weighted median of the timestamps of the valid votes in the block.LastCommit. For height == 1, it's genesis time.

The request transaction bytes.

txhash?: string

The transaction hash.