Transaction Details
Tx hash
071c01aacb10e8513047dd47fe29a04928dbc11add4d4427c641a831f57d58ca
Tx prefix hash
5443978c52765d74f5d530b911204cbed0f32476985ef1752fa47b4bf375adc7
Tx public key
d803e79ea417d60590b2e2fc6cdb3e3664bcb63cc4f5ffe111349fe9d5ddcc4e
Age [y:d:h:m:s]
05:255:13:06:47
Timestamp [UCT] (epoch)
2019-01-26 04:17:50 (1548476270)
Block
98919 (1464397 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d803e79ea417d60590b2e2fc6cdb3e3664bcb63cc4f5ffe111349fe9d5ddcc4e032100bc1cab216318c4083e6bf86ede177ffac7109ef6eae3c776fa34a31835d39223021b00000000000000000000000000c5a3caf700000000000000000000
Outputs
1 output(s) for total of 19.331930518 ARQ
stealth address amount amount idx
00: c7a13ea7d640e8631724a3d1b9fc318234eb18866c3a70ed9110e2588c7886c4 19.331930518 488668 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": 98937, 
  "vin": [ {
      "gen": {
        "height": 98919
      }
    }
  ], 
  "vout": [ {
      "amount": 19331930518, 
      "target": {
        "key": "c7a13ea7d640e8631724a3d1b9fc318234eb18866c3a70ed9110e2588c7886c4"
      }
    }
  ], 
  "extra": [ 1, 216, 3, 231, 158, 164, 23, 214, 5, 144, 178, 226, 252, 108, 219, 62, 54, 100, 188, 182, 60, 196, 245, 255, 225, 17, 52, 159, 233, 213, 221, 204, 78, 3, 33, 0, 188, 28, 171, 33, 99, 24, 196, 8, 62, 107, 248, 110, 222, 23, 127, 250, 199, 16, 158, 246, 234, 227, 199, 118, 250, 52, 163, 24, 53, 211, 146, 35, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 197, 163, 202, 247, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}