Transaction Details
Tx hash
59132170fff04d420c504c0ff6a70fe7766584f2f5ffd4f82e36e1fdfc0b8fdf
Tx prefix hash
dec8247cd53c7186cd7f1e3efb39ac3d72583388c45ce9b576257b4a8ea6ea19
Tx public key
4a6ac3c1d886c4f73a102c90351cd0b5c3aa8ea45333dc0acd1ebbc2b48ca5f4
Age [y:d:h:m:s]
05:173:15:21:26
Timestamp [UCT] (epoch)
2019-06-01 08:36:01 (1559378161)
Block
188950 (1405577 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014a6ac3c1d886c4f73a102c90351cd0b5c3aa8ea45333dc0acd1ebbc2b48ca5f4032100a0c23c2b38a992ff438e73515aa13de9af81fe3f9a5dbedfa12c3bcf4c98c9d8021b00000000000000000000000000086a3b9d00000000000000000000
Outputs
1 output(s) for total of 18.519734187 ARQ
stealth address amount amount idx
00: 45b6ac43eefc0667b5d91fbb07f31f65b1ca4d7e4b5b25bace7567c0c78f9798 18.519734187 850435 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": 188968, 
  "vin": [ {
      "gen": {
        "height": 188950
      }
    }
  ], 
  "vout": [ {
      "amount": 18519734187, 
      "target": {
        "key": "45b6ac43eefc0667b5d91fbb07f31f65b1ca4d7e4b5b25bace7567c0c78f9798"
      }
    }
  ], 
  "extra": [ 1, 74, 106, 195, 193, 216, 134, 196, 247, 58, 16, 44, 144, 53, 28, 208, 181, 195, 170, 142, 164, 83, 51, 220, 10, 205, 30, 187, 194, 180, 140, 165, 244, 3, 33, 0, 160, 194, 60, 43, 56, 169, 146, 255, 67, 142, 115, 81, 90, 161, 61, 233, 175, 129, 254, 63, 154, 93, 190, 223, 161, 44, 59, 207, 76, 152, 201, 216, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 8, 106, 59, 157, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}