Transaction Details
Tx hash
5d862fe345c7062fa6999226366a5b50ea617f37e6bed86d42fa5ebdf0abca15
Tx prefix hash
9e5aa2e1591b8b4b26a639f045226e9d036a72b03dffd5fdb312d0d6ed5e20e4
Tx public key
5c0b9cefec044d9d7482a6bcf9cb959ddb592a0eecdf6d286a89ed0928a70e81
Age [y:d:h:m:s]
05:149:01:31:09
Timestamp [UCT] (epoch)
2019-05-07 23:05:20 (1557270320)
Block
171601 (1388430 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
015c0b9cefec044d9d7482a6bcf9cb959ddb592a0eecdf6d286a89ed0928a70e81032100b6af389b5d0b9fea98e954039e4b19ed005ef7a5814fcf1e096963aa404ef7b5021b000000000000000000000000005f01d3b100000000000000000000
Outputs
1 output(s) for total of 18.673412555 ARQ
stealth address amount amount idx
00: b869d45a89f070706e0d9cad1621d6008e187b2c9b97d355d166a98515e25c1b 18.673412555 778697 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": 171619, 
  "vin": [ {
      "gen": {
        "height": 171601
      }
    }
  ], 
  "vout": [ {
      "amount": 18673412555, 
      "target": {
        "key": "b869d45a89f070706e0d9cad1621d6008e187b2c9b97d355d166a98515e25c1b"
      }
    }
  ], 
  "extra": [ 1, 92, 11, 156, 239, 236, 4, 77, 157, 116, 130, 166, 188, 249, 203, 149, 157, 219, 89, 42, 14, 236, 223, 109, 40, 106, 137, 237, 9, 40, 167, 14, 129, 3, 33, 0, 182, 175, 56, 155, 93, 11, 159, 234, 152, 233, 84, 3, 158, 75, 25, 237, 0, 94, 247, 165, 129, 79, 207, 30, 9, 105, 99, 170, 64, 78, 247, 181, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 95, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}