Transaction Details
Tx hash
9ad931dc48ebbe396769f7b85cb71cf6c7552331cb09e143121b4941311de1ce
Tx prefix hash
be97624815d80c280f1d0d78f4d442a682a367ef14fb4894f545c120b6d568b0
Tx public key
cf3540873a1fe9a4a5915d900b6068761f6223a90779a1afdbf4438493aca624
Age [y:d:h:m:s]
05:052:15:36:58
Timestamp [UCT] (epoch)
2019-10-06 15:08:30 (1570374510)
Block
279736 (1319257 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01cf3540873a1fe9a4a5915d900b6068761f6223a90779a1afdbf4438493aca624032100c7e667a88626d2fbd1206d11b963fcee1a0a36c50505ce25f6d8532234770a00021b000000000000000000000000006130b1bd00000000000000000000
Outputs
1 output(s) for total of 20.130535394 ARQ
stealth address amount amount idx
00: f494f4fa7695cf9cdcc39eac462eefbd93e292caf18e7f34d1d957e016ce90a2 20.130535394 1259376 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": 279754, 
  "vin": [ {
      "gen": {
        "height": 279736
      }
    }
  ], 
  "vout": [ {
      "amount": 20130535394, 
      "target": {
        "key": "f494f4fa7695cf9cdcc39eac462eefbd93e292caf18e7f34d1d957e016ce90a2"
      }
    }
  ], 
  "extra": [ 1, 207, 53, 64, 135, 58, 31, 233, 164, 165, 145, 93, 144, 11, 96, 104, 118, 31, 98, 35, 169, 7, 121, 161, 175, 219, 244, 67, 132, 147, 172, 166, 36, 3, 33, 0, 199, 230, 103, 168, 134, 38, 210, 251, 209, 32, 109, 17, 185, 99, 252, 238, 26, 10, 54, 197, 5, 5, 206, 37, 246, 216, 83, 34, 52, 119, 10, 0, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 97, 48, 177, 189, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}