Transaction Details
Tx hash
561b1d612239bad4da8750b26c4dbbdafcf9f6bea0817a400bd2d3500dfebfb1
Tx prefix hash
bf9f7fd3b70b1c070ef49473f1a75d0e4ef85b24c859af5920e4913d0230a15a
Tx public key
39f4bbf63d22dd08eba113b56858314c83da381e6e59bf38cf6394a692d5bbdb
Age [y:d:h:m:s]
05:005:16:25:31
Timestamp [UCT] (epoch)
2019-07-03 22:50:52 (1562194252)
Block
212250 (1286587 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0139f4bbf63d22dd08eba113b56858314c83da381e6e59bf38cf6394a692d5bbdb021100000010ee3c55ab000000000000000000032100aa07dd82ea2b14a48b384ffa160b09963dc05eb2cead72accf75c6fd92a3bad0
Outputs
1 output(s) for total of 18.314995796 ARQ
stealth address amount amount idx
00: 601cf4e87d294cc42084528c4923c70cc8b0ed909a75c7cef1991fd499246ac3 18.314995796 980154 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": 212268, 
  "vin": [ {
      "gen": {
        "height": 212250
      }
    }
  ], 
  "vout": [ {
      "amount": 18314995796, 
      "target": {
        "key": "601cf4e87d294cc42084528c4923c70cc8b0ed909a75c7cef1991fd499246ac3"
      }
    }
  ], 
  "extra": [ 1, 57, 244, 187, 246, 61, 34, 221, 8, 235, 161, 19, 181, 104, 88, 49, 76, 131, 218, 56, 30, 110, 89, 191, 56, 207, 99, 148, 166, 146, 213, 187, 219, 2, 17, 0, 0, 0, 16, 238, 60, 85, 171, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 170, 7, 221, 130, 234, 43, 20, 164, 139, 56, 79, 250, 22, 11, 9, 150, 61, 192, 94, 178, 206, 173, 114, 172, 207, 117, 198, 253, 146, 163, 186, 208
  ], 
  "rct_signatures": {
    "type": 0
  }
}