Transaction Details
Tx hash
d24d7f363470b9b0bd1d743cca2bdf2eb7d2a288055d4c291271fef1472f3e87
Tx prefix hash
db4d2a09008acc840b7eb319816dcb9656a95f2c6f770d91cca884c9f8b5f17f
Tx public key
0e5e7b46fe806e00b1f2356a87ca904f36d213feea2488d3d92643a62f2a6dae
Age [y:d:h:m:s]
05:327:07:13:49
Timestamp [UCT] (epoch)
2019-01-04 11:10:38 (1546600238)
Block
83461 (1515165 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010e5e7b46fe806e00b1f2356a87ca904f36d213feea2488d3d92643a62f2a6dae032100b6bcccf4634ea105fc7a2ffda08b40bd96494047e8a150e48879fd8838eb38e7021b0000000000000000000000000031c7391c00000000000000000000
Outputs
1 output(s) for total of 19.474951676 ARQ
stealth address amount amount idx
00: c73edd5afc6335d984a9931731cb252d65b19ae7a3a1c77c1a307ba1cdf176fd 19.474951676 413703 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": 83479, 
  "vin": [ {
      "gen": {
        "height": 83461
      }
    }
  ], 
  "vout": [ {
      "amount": 19474951676, 
      "target": {
        "key": "c73edd5afc6335d984a9931731cb252d65b19ae7a3a1c77c1a307ba1cdf176fd"
      }
    }
  ], 
  "extra": [ 1, 14, 94, 123, 70, 254, 128, 110, 0, 177, 242, 53, 106, 135, 202, 144, 79, 54, 210, 19, 254, 234, 36, 136, 211, 217, 38, 67, 166, 47, 42, 109, 174, 3, 33, 0, 182, 188, 204, 244, 99, 78, 161, 5, 252, 122, 47, 253, 160, 139, 64, 189, 150, 73, 64, 71, 232, 161, 80, 228, 136, 121, 253, 136, 56, 235, 56, 231, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 49, 199, 57, 28, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}