Transaction Details
Tx hash
fa086fddc0e9dc7c8ad98a78baec01bf310f1a5b0eb8d2d1b856f4c5349454ee
Tx prefix hash
125e30f9a6d3156872d79189f3a07af633b904f2af1a69d0b1b1d2982be83de0
Tx public key
44e5278e61f5d4c6f48c409e600efcf63dc067b4a5cf5a4cedead6060068b526
Age [y:d:h:m:s]
05:049:04:53:46
Timestamp [UCT] (epoch)
2019-08-15 17:45:42 (1565891142)
Block
243021 (1316955 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0144e5278e61f5d4c6f48c409e600efcf63dc067b4a5cf5a4cedead6060068b526032100d3da38a6f70a20d5907f654a1e909fd13ffc9285234b9b618b407d90d8dab109021b00000000000000000000000015671522be00000000000000000000
Outputs
1 output(s) for total of 18.048182834 ARQ
stealth address amount amount idx
00: c0fb3c3ba8c1368004635e7881c39471c5ab74a39ea793e62b3a64f6c7f8f558 18.048182834 1101518 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": 243039, 
  "vin": [ {
      "gen": {
        "height": 243021
      }
    }
  ], 
  "vout": [ {
      "amount": 18048182834, 
      "target": {
        "key": "c0fb3c3ba8c1368004635e7881c39471c5ab74a39ea793e62b3a64f6c7f8f558"
      }
    }
  ], 
  "extra": [ 1, 68, 229, 39, 142, 97, 245, 212, 198, 244, 140, 64, 158, 96, 14, 252, 246, 61, 192, 103, 180, 165, 207, 90, 76, 237, 234, 214, 6, 0, 104, 181, 38, 3, 33, 0, 211, 218, 56, 166, 247, 10, 32, 213, 144, 127, 101, 74, 30, 144, 159, 209, 63, 252, 146, 133, 35, 75, 155, 97, 139, 64, 125, 144, 216, 218, 177, 9, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21, 103, 21, 34, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}