Transaction Details
Tx hash
a4c3d44168658f4b4f41df37675e55522de3e00bd0543601902ddfea144184f0
Tx prefix hash
dec991a9d1de5acaec2700a0da0370f8b1dc27eac5d7aa8782662bd24192f6a9
Tx public key
c22f1cbec4b9834d710d8cef1af6fe12f3e9fb8a71bc4dfbb2d0c8c79297cf0e
Age [y:d:h:m:s]
05:205:13:34:33
Timestamp [UCT] (epoch)
2019-05-11 13:31:39 (1557581499)
Block
174126 (1428260 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c22f1cbec4b9834d710d8cef1af6fe12f3e9fb8a71bc4dfbb2d0c8c79297cf0e0321002172e5074ee8e3c97e3c60cb1aefa6e3306e4d1dc687afe331c91af2d93d62c5021b000000000000000000000000011201d3b100000000000000000000
Outputs
1 output(s) for total of 18.650943032 ARQ
stealth address amount amount idx
00: 178f78e5ddcb84ed6ddf49fb52c844ac4785c38e6ac1ecb3e6eb66b656257710 18.650943032 788163 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": 174144, 
  "vin": [ {
      "gen": {
        "height": 174126
      }
    }
  ], 
  "vout": [ {
      "amount": 18650943032, 
      "target": {
        "key": "178f78e5ddcb84ed6ddf49fb52c844ac4785c38e6ac1ecb3e6eb66b656257710"
      }
    }
  ], 
  "extra": [ 1, 194, 47, 28, 190, 196, 185, 131, 77, 113, 13, 140, 239, 26, 246, 254, 18, 243, 233, 251, 138, 113, 188, 77, 251, 178, 208, 200, 199, 146, 151, 207, 14, 3, 33, 0, 33, 114, 229, 7, 78, 232, 227, 201, 126, 60, 96, 203, 26, 239, 166, 227, 48, 110, 77, 29, 198, 135, 175, 227, 49, 201, 26, 242, 217, 61, 98, 197, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 18, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}