Decode a Transaction with the Flow CLI

Updated: 2022/10/21 by

1 min read

How to decode a Flow transaction from the command line

The Flow CLI provides a command to decode a transaction from RLP in a file. It uses same transaction format as get command

1
flow transactions decode <file>

Example Usage

1
> flow transactions decode ./rlp-file.rlp 
2

3
ID		c1a52308fb906358d4a33c1f1d5fc458d3cfea0d570a51a9dea915b90d678346
4
Payer		83de1a7075f190a1
5
Authorizers	[83de1a7075f190a1]
6

7
Proposal Key:	
8
    Address	    83de1a7075f190a1
9
    Index	    1
10
    Sequence	1
11

12
No Payload Signatures
13

14
Envelope Signature 0: 83de1a7075f190a1
15
Signatures (minimized, use --include signatures)
16

17
Code (hidden, use --include code)
18

19
Payload (hidden, use --include payload)

Arguments

Filename

Name: <file_name>
Valid Input: file name.

The first argument is the filename containing the transaction RLP.

Flags

Include Fields

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

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

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

Version Check

Flag: --skip-version-check
Default: false

Skip version check during start up to speed up process for slow connections.