Get a Transaction with the Flow CLI

How to get a Flow transaction from the command line

The Flow CLI provides a command to fetch a transaction that was previously submitted to an Access API.

1
flow transactions get <tx_id>

Example Usage

1
> flow transactions get 40bc4b100c1930c61381c22e0f4c10a7f5827975ee25715527c1061b8d71e5aa --network mainnet
2
3
Status ✅ SEALED
4
ID 40bc4b100c1930c61381c22e0f4c10a7f5827975ee25715527c1061b8d71e5aa
5
Payer 18eb4ee6b3c026d2
6
Authorizers [18eb4ee6b3c026d2]
7
8
Proposal Key:
9
Address 18eb4ee6b3c026d2
10
Index 11
11
Sequence 17930
12
13
Payload Signature 0: 18eb4ee6b3c026d2
14
Payload Signature 1: 18eb4ee6b3c026d2
15
Envelope Signature 0: 18eb4ee6b3c026d2
16
Signatures (minimized, use --include signatures)
17
18
Events:
19
Index 0
20
Type A.1654653399040a61.FlowToken.TokensWithdrawn
21
Tx ID 40bc4b100c1930c61381c22e0f4c10a7f5827975ee25715527c1061b8d71e5aa
22
Values
23
- amount (UFix64): 0.00100000
24
- from ({}?): 18eb4ee6b3c026d2
25
26
Index 1
27
Type A.1654653399040a61.FlowToken.TokensDeposited
28
Tx ID 40bc4b100c1930c61381c22e0f4c10a7f5827975ee25715527c1061b8d71e5aa
29
Values
30
- amount (UFix64): 0.00100000
31
- to ({}?): 5068e27f275c546c
32
33
Index 2
34
Type A.18eb4ee6b3c026d2.PrivateReceiverForwarder.PrivateDeposit
35
Tx ID 40bc4b100c1930c61381c22e0f4c10a7f5827975ee25715527c1061b8d71e5aa
36
Values
37
- amount (UFix64): 0.00100000
38
- to ({}?): 5068e27f275c546c
39
40
41
42
Code (hidden, use --include code)
43
44
Payload (hidden, use --include payload)

Arguments

Transaction ID

  • Name: <tx_id>
  • Valid Input: transaction ID.

The first argument is the ID (hash) of the transaction.

Flags

Include Fields

  • Flag: --include
  • Valid inputs: code, payload, signatures

Specify fields to include in the result output. Applies only to the text output.

Code

  • Flag: --code

⚠️ Deprecated: use include flag.

Wait for Seal

  • Flag: --sealed
  • Default: false

Indicate whether to wait for the transaction to be sealed before displaying the result.

Exclude Fields

  • Flag: --exclude
  • Valid inputs: events

Specify fields to exclude from the result output. Applies only to the text output.

Host

  • Flag: --host
  • Valid inputs: an IP address or hostname.
  • Default: 127.0.0.1:3569 (Flow Emulator)

Specify the hostname of the Access API that will be used to execute the command. This flag overrides any host defined by the --network flag.

Network Key

  • Flag: --network-key
  • Valid inputs: A valid network public key of the host in hex string format

Specify the network public key of the Access API that will be used to create a secure GRPC client when executing the command.

Network

  • Flag: --network
  • Short Flag: -n
  • Valid inputs: the name of a network defined in the configuration (flow.json)
  • Default: emulator

Specify which network you want the command to use for execution.

Filter

  • Flag: --filter
  • Short Flag: -x
  • Valid inputs: a case-sensitive name of the result property.

Specify any property name from the result you want to return as the only value.

Output

  • Flag: --output
  • Short Flag: -o
  • Valid inputs: json, inline

Specify the format of the command results.

Save

  • Flag: --save
  • Short Flag: -s
  • Valid inputs: a path in the current filesystem.

Specify the filename where you want the result to be saved

Log

  • Flag: --log
  • Short Flag: -l
  • Valid inputs: none, error, debug
  • Default: info

Specify the log level. Control how much output you want to see during command execution.

Configuration

  • Flag: --config-path
  • Short Flag: -f
  • Valid inputs: a path in the current filesystem.
  • Default: flow.json

Specify the path to the flow.json configuration file. You can use the -f flag multiple times to merge several configuration files.