Transaction Details
Tx hash
704c4b850421abb43eeb7ca2ac77fd709c741d145b515a51859e449a3e0da845
Tx prefix hash
0b1ccaaae79dbeb159d13d25f8840ea9229953fa112df6eabdb938e57bfb0a8b
Tx public key
b206710f059674eb1cc90fdbbf5fce19c687d20b313036b9f60dac606ecb50bf
Age [y:d:h:m:s]
05:304:21:57:50
Timestamp [UCT] (epoch)
2019-01-26 02:26:37 (1548469597)
Block
98855 (1499237 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01b206710f059674eb1cc90fdbbf5fce19c687d20b313036b9f60dac606ecb50bf03210003c897dbfcdd5c1b0e39469709b80103f9c081d2f3d285ffad2cf59671e9e91602100000000b191602000000000000000000
Outputs
1 output(s) for total of 19.332590151 ARQ
stealth address amount amount idx
00: f96d73de1275330a0d3b34bfc8197d2d134206eed3c9df85684e8aae53a65e3e 19.332590151 488370 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": 98873, 
  "vin": [ {
      "gen": {
        "height": 98855
      }
    }
  ], 
  "vout": [ {
      "amount": 19332590151, 
      "target": {
        "key": "f96d73de1275330a0d3b34bfc8197d2d134206eed3c9df85684e8aae53a65e3e"
      }
    }
  ], 
  "extra": [ 1, 178, 6, 113, 15, 5, 150, 116, 235, 28, 201, 15, 219, 191, 95, 206, 25, 198, 135, 210, 11, 49, 48, 54, 185, 246, 13, 172, 96, 110, 203, 80, 191, 3, 33, 0, 3, 200, 151, 219, 252, 221, 92, 27, 14, 57, 70, 151, 9, 184, 1, 3, 249, 192, 129, 210, 243, 210, 133, 255, 173, 44, 245, 150, 113, 233, 233, 22, 2, 16, 0, 0, 0, 11, 25, 22, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}