Transaction Details
Tx hash
8efa2eb79741b101d8dfd1f76b81e6715275b2a0182332ecf88ecc4ec4ec4b92
Tx prefix hash
a98d141359012a589ed4d25a9e82b9f0cc92e00d1458a56c072ef089fb3b45f8
Tx public key
3c63e8642d856bcab2059c559c0e4d4ac818c6af05683c70ff27eac9ea6fe7b3
Age [y:d:h:m:s]
05:110:07:36:15
Timestamp [UCT] (epoch)
2019-08-10 03:51:12 (1565409072)
Block
239026 (1360101 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013c63e8642d856bcab2059c559c0e4d4ac818c6af05683c70ff27eac9ea6fe7b3032100b52182e7cdc728081e5078b9d231c2a009fea2e6491e1eaf4c9cb9149b784aa3021b000000000000000000000000040afd0e1700000000000000000000
Outputs
1 output(s) for total of 18.082596757 ARQ
stealth address amount amount idx
00: 64fda4da676aeb7f22c9c8f74fdfb4ea7c84583c1ddaf8b6d2178f67f17ddc0a 18.082596757 1094122 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": 239044, 
  "vin": [ {
      "gen": {
        "height": 239026
      }
    }
  ], 
  "vout": [ {
      "amount": 18082596757, 
      "target": {
        "key": "64fda4da676aeb7f22c9c8f74fdfb4ea7c84583c1ddaf8b6d2178f67f17ddc0a"
      }
    }
  ], 
  "extra": [ 1, 60, 99, 232, 100, 45, 133, 107, 202, 178, 5, 156, 85, 156, 14, 77, 74, 200, 24, 198, 175, 5, 104, 60, 112, 255, 39, 234, 201, 234, 111, 231, 179, 3, 33, 0, 181, 33, 130, 231, 205, 199, 40, 8, 30, 80, 120, 185, 210, 49, 194, 160, 9, 254, 162, 230, 73, 30, 30, 175, 76, 156, 185, 20, 155, 120, 74, 163, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 10, 253, 14, 23, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}