Transaction Details
Tx hash
7075ad603e9eddbc31ab2e11773ae5501992f7aea76cd61d3dc4d28aad6de2d3
Tx prefix hash
889388f92d98315f371ba183bd9328e6a840df5987047ccbdb69c9a87e1c5b4e
Tx public key
b12ebd8c9f71e5c0ac1444fbdc96933b87d2731800e858551a499654d81118da
Age [y:d:h:m:s]
05:285:04:23:27
Timestamp [UCT] (epoch)
2019-02-18 23:28:01 (1550532481)
Block
115943 (1485074 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01b12ebd8c9f71e5c0ac1444fbdc96933b87d2731800e858551a499654d81118da0321001388ddc6d1dbe56cd44df5761db8f5b0fddc106101da43a58c4e5a0be9aae584021b000000000000000000000000000bbe3adb00000000000000000000
Outputs
1 output(s) for total of 19.175635903 ARQ
stealth address amount amount idx
00: cf2469171f99655519beebb29fc7a25949e83f649d7466711e1d769333439c47 19.175635903 564105 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": 115961, 
  "vin": [ {
      "gen": {
        "height": 115943
      }
    }
  ], 
  "vout": [ {
      "amount": 19175635903, 
      "target": {
        "key": "cf2469171f99655519beebb29fc7a25949e83f649d7466711e1d769333439c47"
      }
    }
  ], 
  "extra": [ 1, 177, 46, 189, 140, 159, 113, 229, 192, 172, 20, 68, 251, 220, 150, 147, 59, 135, 210, 115, 24, 0, 232, 88, 85, 26, 73, 150, 84, 216, 17, 24, 218, 3, 33, 0, 19, 136, 221, 198, 209, 219, 229, 108, 212, 77, 245, 118, 29, 184, 245, 176, 253, 220, 16, 97, 1, 218, 67, 165, 140, 78, 90, 11, 233, 170, 229, 132, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 190, 58, 219, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}