Transaction Details
Tx hash
8eeb8bd3e74976cf4f6905d8bf13c7a7fb92514b11a749c471623db94fcc80d7
Tx prefix hash
bbf0ea57b9063a273f074a1bb1898768400c6c0f6232fc00b2b6436395a69422
Tx public key
9962b2cd7270bd5c23c0b6c7df94f38ef98304c5e1362d6a3b2bcf196d0bc9b0
Age [y:d:h:m:s]
05:057:10:49:08
Timestamp [UCT] (epoch)
2019-08-10 16:27:47 (1565454467)
Block
239410 (1322769 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019962b2cd7270bd5c23c0b6c7df94f38ef98304c5e1362d6a3b2bcf196d0bc9b003210077bc6eae3be97e339f075493c5c45dacc99bb3384817dfe797c5c3db47e41e90021b00000000000000000000000005e2e9dd3400000000000000000000
Outputs
1 output(s) for total of 18.079286037 ARQ
stealth address amount amount idx
00: e1c5c4f3fe651b9b60aae6248d3fb86b733fe4a89b72f657b0e6b6cf51dfd701 18.079286037 1094868 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": 239428, 
  "vin": [ {
      "gen": {
        "height": 239410
      }
    }
  ], 
  "vout": [ {
      "amount": 18079286037, 
      "target": {
        "key": "e1c5c4f3fe651b9b60aae6248d3fb86b733fe4a89b72f657b0e6b6cf51dfd701"
      }
    }
  ], 
  "extra": [ 1, 153, 98, 178, 205, 114, 112, 189, 92, 35, 192, 182, 199, 223, 148, 243, 142, 249, 131, 4, 197, 225, 54, 45, 106, 59, 43, 207, 25, 109, 11, 201, 176, 3, 33, 0, 119, 188, 110, 174, 59, 233, 126, 51, 159, 7, 84, 147, 197, 196, 93, 172, 201, 155, 179, 56, 72, 23, 223, 231, 151, 197, 195, 219, 71, 228, 30, 144, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 226, 233, 221, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}