Transaction Details
Tx hash
a50514ff4207b796a1a178d2cfd29f192b60cc853e6805f3ec864b60aa946341
Tx prefix hash
2c5e1000a9c72803d8567da08a9fbb87d171feaa22cccf2f53ba84e5b607cf19
Tx public key
dd5e060b3a29895dfdd13e33da22a764ef88369a685704d6c74dc92664799223
Age [y:d:h:m:s]
05:268:03:02:14
Timestamp [UCT] (epoch)
2019-01-13 14:19:49 (1547389189)
Block
89960 (1473354 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01dd5e060b3a29895dfdd13e33da22a764ef88369a685704d6c74dc92664799223032100a95ae4da59e4409b06465999096024af591e92073ab04dfc86e8ca06c625321d021b000000000000000000000000001e79412400000000000000000000
Outputs
1 output(s) for total of 19.414716202 ARQ
stealth address amount amount idx
00: d23f4d724333d3375c70407cee76cb92eb04f73eac9e74193eef00761a0d28df 19.414716202 444518 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": 89978, 
  "vin": [ {
      "gen": {
        "height": 89960
      }
    }
  ], 
  "vout": [ {
      "amount": 19414716202, 
      "target": {
        "key": "d23f4d724333d3375c70407cee76cb92eb04f73eac9e74193eef00761a0d28df"
      }
    }
  ], 
  "extra": [ 1, 221, 94, 6, 11, 58, 41, 137, 93, 253, 209, 62, 51, 218, 34, 167, 100, 239, 136, 54, 154, 104, 87, 4, 214, 199, 77, 201, 38, 100, 121, 146, 35, 3, 33, 0, 169, 90, 228, 218, 89, 228, 64, 155, 6, 70, 89, 153, 9, 96, 36, 175, 89, 30, 146, 7, 58, 176, 77, 252, 134, 232, 202, 6, 198, 37, 50, 29, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 30, 121, 65, 36, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}