Transaction Details
Tx hash
569c32c8f93c47fd3b8f82861cc0cdf9d86c2ef479562c7c7eca177c2e401843
Tx prefix hash
8f44f64a7425e5ce0167e75ccc3debf584747ad002eb5deb5d99e58e2c2d7b25
Tx public key
1fa897b4f86cf9aa0f3a20aa7fc819122b7a4f9aeb8ba27db2101f0c7577892c
Age [y:d:h:m:s]
05:272:23:59:46
Timestamp [UCT] (epoch)
2019-01-07 22:39:42 (1546900782)
Block
85948 (1476809 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011fa897b4f86cf9aa0f3a20aa7fc819122b7a4f9aeb8ba27db2101f0c7577892c032100fa9b38e9f5001f979c4e28bfcbe27943cb95c1b735d33d4a1c55ef7e6f5b036b021b000000000000000000000000001cd5b34f00000000000000000000
Outputs
1 output(s) for total of 19.451870130 ARQ
stealth address amount amount idx
00: 85c644e09e5c9aaf35b9e115946e412a02ab6adda7738f04592e8ec64e4bd86d 19.451870130 425010 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": 85966, 
  "vin": [ {
      "gen": {
        "height": 85948
      }
    }
  ], 
  "vout": [ {
      "amount": 19451870130, 
      "target": {
        "key": "85c644e09e5c9aaf35b9e115946e412a02ab6adda7738f04592e8ec64e4bd86d"
      }
    }
  ], 
  "extra": [ 1, 31, 168, 151, 180, 248, 108, 249, 170, 15, 58, 32, 170, 127, 200, 25, 18, 43, 122, 79, 154, 235, 139, 162, 125, 178, 16, 31, 12, 117, 119, 137, 44, 3, 33, 0, 250, 155, 56, 233, 245, 0, 31, 151, 156, 78, 40, 191, 203, 226, 121, 67, 203, 149, 193, 183, 53, 211, 61, 74, 28, 85, 239, 126, 111, 91, 3, 107, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 28, 213, 179, 79, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}