Transaction Details
Tx hash
114392e8ea39481b05633e85d6c8ad3eae0c775243165ee69f6b63116a9b2633
Tx prefix hash
dcfccb9582d35cb4dd854a3468873bb28e9f0d467919b2f76153a15252895da9
Tx public key
d20c7749030671e53a678310058dbc8289cb813a74927f30328f420f0cc67c51
Age [y:d:h:m:s]
05:121:23:32:51
Timestamp [UCT] (epoch)
2019-07-31 13:21:21 (1564579281)
Block
232108 (1368480 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d20c7749030671e53a678310058dbc8289cb813a74927f30328f420f0cc67c51032100b37fab3f268ba302faffc5f548bb63e324fe0ce955ed3953bada7b6d675be97d021b00000000000000000000000007197975fa00000000000000000000
Outputs
1 output(s) for total of 18.142345402 ARQ
stealth address amount amount idx
00: 4ce8304dfa0600fd70dea0ea6971f375b9166ad64b791f38e959f9e5d23c3fe3 18.142345402 1078878 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": 232126, 
  "vin": [ {
      "gen": {
        "height": 232108
      }
    }
  ], 
  "vout": [ {
      "amount": 18142345402, 
      "target": {
        "key": "4ce8304dfa0600fd70dea0ea6971f375b9166ad64b791f38e959f9e5d23c3fe3"
      }
    }
  ], 
  "extra": [ 1, 210, 12, 119, 73, 3, 6, 113, 229, 58, 103, 131, 16, 5, 141, 188, 130, 137, 203, 129, 58, 116, 146, 127, 48, 50, 143, 66, 15, 12, 198, 124, 81, 3, 33, 0, 179, 127, 171, 63, 38, 139, 163, 2, 250, 255, 197, 245, 72, 187, 99, 227, 36, 254, 12, 233, 85, 237, 57, 83, 186, 218, 123, 109, 103, 91, 233, 125, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 25, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}