Transaction Details
Tx hash
4b619479adb8253603d23905e1283527d1966bd782c68163e6f53d9c86cbdf7b
Tx prefix hash
cdb6acfb31267f5723ce18b4cc012e1078eda6107c676df6a6f75c4304b260b9
Tx public key
4a2f44b4fa7f27f5e643e0adcfeddde0e1cac9a3d1f9f6b9abd55a27f6512b0c
Age [y:d:h:m:s]
05:203:20:18:51
Timestamp [UCT] (epoch)
2019-03-13 22:29:37 (1552516177)
Block
132330 (1427528 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014a2f44b4fa7f27f5e643e0adcfeddde0e1cac9a3d1f9f6b9abd55a27f6512b0c032100cf9284c25e54637a49e04d1e62dacebbdc4dd1b7c722ed73a6e9e56b6c60755e021b0000000000000000000000000001cd497c00000000000000000000
Outputs
1 output(s) for total of 19.026383099 ARQ
stealth address amount amount idx
00: c2700c62babe76dbf4c95190185eb1e05d87d58aa1309e2ec109e7ca51099e2d 19.026383099 625383 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": 132348, 
  "vin": [ {
      "gen": {
        "height": 132330
      }
    }
  ], 
  "vout": [ {
      "amount": 19026383099, 
      "target": {
        "key": "c2700c62babe76dbf4c95190185eb1e05d87d58aa1309e2ec109e7ca51099e2d"
      }
    }
  ], 
  "extra": [ 1, 74, 47, 68, 180, 250, 127, 39, 245, 230, 67, 224, 173, 207, 237, 221, 224, 225, 202, 201, 163, 209, 249, 246, 185, 171, 213, 90, 39, 246, 81, 43, 12, 3, 33, 0, 207, 146, 132, 194, 94, 84, 99, 122, 73, 224, 77, 30, 98, 218, 206, 187, 220, 77, 209, 183, 199, 34, 237, 115, 166, 233, 229, 107, 108, 96, 117, 94, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 205, 73, 124, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}