Transaction Details
Tx hash
60993a95b79a60c5558c3fd5bc1d3263888f681826ca725bbe4377e6c46bd5ee
Tx prefix hash
e0dc6a69bb4e4f1edf3b6b7c74214d930065850323ae7e4e9ed598f90670ff2a
Tx public key
e05e6f1f0ef1e1f6847f1f6c1fae574c0236c16cf87a29ea1bf2f6ac4a18b0fd
Age [y:d:h:m:s]
05:330:01:53:16
Timestamp [UCT] (epoch)
2019-01-05 02:43:10 (1546656190)
Block
83941 (1517099 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e05e6f1f0ef1e1f6847f1f6c1fae574c0236c16cf87a29ea1bf2f6ac4a18b0fd032100c4571d71205774bf843c18ba459c41122f1129dd58ea2dd3f19486931386efc3021b0000000000000000000000000030b8e05600000000000000000000
Outputs
1 output(s) for total of 19.470658312 ARQ
stealth address amount amount idx
00: 8f2694e959d47447e09762eaae8c1419af23c2bf9ee43e13d2fb38c09620caef 19.470658312 416037 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": 83959, 
  "vin": [ {
      "gen": {
        "height": 83941
      }
    }
  ], 
  "vout": [ {
      "amount": 19470658312, 
      "target": {
        "key": "8f2694e959d47447e09762eaae8c1419af23c2bf9ee43e13d2fb38c09620caef"
      }
    }
  ], 
  "extra": [ 1, 224, 94, 111, 31, 14, 241, 225, 246, 132, 127, 31, 108, 31, 174, 87, 76, 2, 54, 193, 108, 248, 122, 41, 234, 27, 242, 246, 172, 74, 24, 176, 253, 3, 33, 0, 196, 87, 29, 113, 32, 87, 116, 191, 132, 60, 24, 186, 69, 156, 65, 18, 47, 17, 41, 221, 88, 234, 45, 211, 241, 148, 134, 147, 19, 134, 239, 195, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 48, 184, 224, 86, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}