Transaction Details
Tx hash
34c17eee14a8f7d0580e92001dadf09e8c6f8add4395ecf2f3794ea97d3e0da3
Tx prefix hash
e6a858f5fde538325a7c3c67213cfa64d0c94ce75c42508dfdab0fb5fea0f97f
Tx public key
77c33a7afdf3474b1c7be56f4030f50b6f3f76a317f9562d30aa7bb75df3218d
Age [y:d:h:m:s]
05:144:12:26:19
Timestamp [UCT] (epoch)
2019-07-09 07:59:07 (1562659147)
Block
216152 (1384645 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0177c33a7afdf3474b1c7be56f4030f50b6f3f76a317f9562d30aa7bb75df3218d021100000032091d2b5c000000000000000000032100c92c3bba2ceb52f54a7d8748546e0142927efd284bace7c364753caa6adf9f3f
Outputs
1 output(s) for total of 18.281016151 ARQ
stealth address amount amount idx
00: f2bbb0262ffe810f06cef8be6b24b7c20cfcddc9ca511553e3e2410a5c6b03b7 18.281016151 1002872 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 216170, 
  "vin": [ {
      "gen": {
        "height": 216152
      }
    }
  ], 
  "vout": [ {
      "amount": 18281016151, 
      "target": {
        "key": "f2bbb0262ffe810f06cef8be6b24b7c20cfcddc9ca511553e3e2410a5c6b03b7"
      }
    }
  ], 
  "extra": [ 1, 119, 195, 58, 122, 253, 243, 71, 75, 28, 123, 229, 111, 64, 48, 245, 11, 111, 63, 118, 163, 23, 249, 86, 45, 48, 170, 123, 183, 93, 243, 33, 141, 2, 17, 0, 0, 0, 50, 9, 29, 43, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 201, 44, 59, 186, 44, 235, 82, 245, 74, 125, 135, 72, 84, 110, 1, 66, 146, 126, 253, 40, 75, 172, 231, 195, 100, 117, 60, 170, 106, 223, 159, 63
  ], 
  "rct_signatures": {
    "type": 0
  }
}