Transaction Details
Tx hash
833d3d4cd3523724a6c500b4bd2123a21662791ba91b8537034fbe1a8ace5eb8
Tx prefix hash
c27e992a7ae4a5979ee7c4dea57df94e6d4932b39b4548e4b32fa005aa2496cb
Tx public key
9f3f1c78d01f59913b14bda9bfc3b4e5ae189c9ae43b12400c02143aa17e3e62
Age [y:d:h:m:s]
05:267:05:53:18
Timestamp [UCT] (epoch)
2019-03-09 23:43:09 (1552174989)
Block
129536 (1472222 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019f3f1c78d01f59913b14bda9bfc3b4e5ae189c9ae43b12400c02143aa17e3e62032100c57f0d3b24a2916f3de2c07e5ac17479d070a98638292ededb756fb2d23bea7b021b00000000000000000000000000109b5a9700000000000000000000
Outputs
1 output(s) for total of 19.051748526 ARQ
stealth address amount amount idx
00: ccb54e38dcccfb5be350d7dddf8b70e019b8ef05990dc5ae17562dee5ad49d34 19.051748526 616363 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": 129554, 
  "vin": [ {
      "gen": {
        "height": 129536
      }
    }
  ], 
  "vout": [ {
      "amount": 19051748526, 
      "target": {
        "key": "ccb54e38dcccfb5be350d7dddf8b70e019b8ef05990dc5ae17562dee5ad49d34"
      }
    }
  ], 
  "extra": [ 1, 159, 63, 28, 120, 208, 31, 89, 145, 59, 20, 189, 169, 191, 195, 180, 229, 174, 24, 156, 154, 228, 59, 18, 64, 12, 2, 20, 58, 161, 126, 62, 98, 3, 33, 0, 197, 127, 13, 59, 36, 162, 145, 111, 61, 226, 192, 126, 90, 193, 116, 121, 208, 112, 169, 134, 56, 41, 46, 222, 219, 117, 111, 178, 210, 59, 234, 123, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 16, 155, 90, 151, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}