Transaction Details
Tx hash
842d205ad18afd64350aff20fd9641ebf698aff17e8d979d08fe63726f0e4976
Tx prefix hash
c252f2b0c9a3353d0afbd2cac23e1338bdd6e3722e610942f97af52468f0557e
Tx public key
85aede0f2c7816cbbb2ecdcf4b7b005810f306953fac243e2186ff8b7ca92f84
Age [y:d:h:m:s]
05:320:23:11:01
Timestamp [UCT] (epoch)
2019-01-13 13:10:26 (1547385026)
Block
89929 (1510641 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0185aede0f2c7816cbbb2ecdcf4b7b005810f306953fac243e2186ff8b7ca92f84032100de6450dd7837a3e35595be5d38027d51d3d95f61c598249274f7e354e6899328021b000000000000000000000000000d79412400000000000000000000
Outputs
1 output(s) for total of 19.415003191 ARQ
stealth address amount amount idx
00: 37713de2e7faeb316a4e56d68ce138b431135bb417f0104c5d43240d50422e02 19.415003191 444353 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": 89947, 
  "vin": [ {
      "gen": {
        "height": 89929
      }
    }
  ], 
  "vout": [ {
      "amount": 19415003191, 
      "target": {
        "key": "37713de2e7faeb316a4e56d68ce138b431135bb417f0104c5d43240d50422e02"
      }
    }
  ], 
  "extra": [ 1, 133, 174, 222, 15, 44, 120, 22, 203, 187, 46, 205, 207, 75, 123, 0, 88, 16, 243, 6, 149, 63, 172, 36, 62, 33, 134, 255, 139, 124, 169, 47, 132, 3, 33, 0, 222, 100, 80, 221, 120, 55, 163, 227, 85, 149, 190, 93, 56, 2, 125, 81, 211, 217, 95, 97, 197, 152, 36, 146, 116, 247, 227, 84, 230, 137, 147, 40, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 13, 121, 65, 36, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}