Transaction Details
Tx hash
636c77af46d480f4a21c6396a9388509d1b3e4203690f40ac97f48cc5f02b006
Tx prefix hash
50b958e52886f2edaee8f71ca467869b6c80f3ae3c3bed7abde4d0083af7c212
Tx public key
1fb7cd47f3a383acebac4df8ea1ae6142fd8fbef075b9c51c5943441b1d53cfb
Age [y:d:h:m:s]
05:298:06:41:14
Timestamp [UCT] (epoch)
2019-02-04 21:40:14 (1549316414)
Block
105884 (1494457 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011fb7cd47f3a383acebac4df8ea1ae6142fd8fbef075b9c51c5943441b1d53cfb032100ff9ad6a9f1732dc3c843fbdc244e26f516e9ef04910e7b6c794690962228fd3e021b00000000000000000000000000281e983e00000000000000000000
Outputs
1 output(s) for total of 19.267909567 ARQ
stealth address amount amount idx
00: d7f9ba817c65e64dbcddbac4143ea998295f614d0e25376f5f4375e3b51f2c18 19.267909567 521643 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": 105902, 
  "vin": [ {
      "gen": {
        "height": 105884
      }
    }
  ], 
  "vout": [ {
      "amount": 19267909567, 
      "target": {
        "key": "d7f9ba817c65e64dbcddbac4143ea998295f614d0e25376f5f4375e3b51f2c18"
      }
    }
  ], 
  "extra": [ 1, 31, 183, 205, 71, 243, 163, 131, 172, 235, 172, 77, 248, 234, 26, 230, 20, 47, 216, 251, 239, 7, 91, 156, 81, 197, 148, 52, 65, 177, 213, 60, 251, 3, 33, 0, 255, 154, 214, 169, 241, 115, 45, 195, 200, 67, 251, 220, 36, 78, 38, 245, 22, 233, 239, 4, 145, 14, 123, 108, 121, 70, 144, 150, 34, 40, 253, 62, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 40, 30, 152, 62, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}