Transaction Details
Tx hash
b3fc6509b9c5d9534b71ce0a7f0b74e144ab2879325c7485a79f03fa043dd4c9
Tx prefix hash
e92ab667683a3a93451e7640a8fff5bc0f983382a599986ebb4e36ac41c05874
Tx public key
badfef7841c7a9a037875372f13fe87755c13e579903041d14a3963e54bbc35c
Age [y:d:h:m:s]
05:094:16:37:53
Timestamp [UCT] (epoch)
2019-08-26 19:04:20 (1566846260)
Block
250980 (1348847 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01badfef7841c7a9a037875372f13fe87755c13e579903041d14a3963e54bbc35c0321009423ff0d3f897b866a3beca930a943e4e5ca23e5b50ba472887fa3234b0ad8f8021b0000000000000000000000001a937716c700000000000000000000
Outputs
1 output(s) for total of 20.408465061 ARQ
stealth address amount amount idx
00: b9b6b0fde8f3dad5782ec7da965e370d916b81bae2735eb19c13b0ad6a7db689 20.408465061 1116351 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": 250998, 
  "vin": [ {
      "gen": {
        "height": 250980
      }
    }
  ], 
  "vout": [ {
      "amount": 20408465061, 
      "target": {
        "key": "b9b6b0fde8f3dad5782ec7da965e370d916b81bae2735eb19c13b0ad6a7db689"
      }
    }
  ], 
  "extra": [ 1, 186, 223, 239, 120, 65, 199, 169, 160, 55, 135, 83, 114, 241, 63, 232, 119, 85, 193, 62, 87, 153, 3, 4, 29, 20, 163, 150, 62, 84, 187, 195, 92, 3, 33, 0, 148, 35, 255, 13, 63, 137, 123, 134, 106, 59, 236, 169, 48, 169, 67, 228, 229, 202, 35, 229, 181, 11, 164, 114, 136, 127, 163, 35, 75, 10, 216, 248, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 26, 147, 119, 22, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}