Transaction Details
Tx hash
8b6e4916f697f64cceaeb6c932213c29eefd7f7da8d2f60a16c9982ab9dc5075
Tx prefix hash
de7c4a57fb4f1d89a6b32d0558f7445b20bdcd309c1ec06bbac6887c58e9054a
Tx public key
095fa3f612d46df9b4654ea0b61b2c1af37361ea6dde58eb758d93f0632bc3f9
Age [y:d:h:m:s]
05:150:17:24:29
Timestamp [UCT] (epoch)
2019-05-06 04:36:00 (1557117360)
Block
170309 (1389648 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01095fa3f612d46df9b4654ea0b61b2c1af37361ea6dde58eb758d93f0632bc3f9032100467ff6ecf216f927871e1cceac57c93f0c8c1b35aaaf7e7c2e5177ae5f484d02021b000000000000000000000000008a01d3b100000000000000000000
Outputs
1 output(s) for total of 18.685002579 ARQ
stealth address amount amount idx
00: 5b62e690a5cf770df7e4e3bd8b8e383c0489abe4a41df7fcd8ecf01dde8fa4bb 18.685002579 773942 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": 170327, 
  "vin": [ {
      "gen": {
        "height": 170309
      }
    }
  ], 
  "vout": [ {
      "amount": 18685002579, 
      "target": {
        "key": "5b62e690a5cf770df7e4e3bd8b8e383c0489abe4a41df7fcd8ecf01dde8fa4bb"
      }
    }
  ], 
  "extra": [ 1, 9, 95, 163, 246, 18, 212, 109, 249, 180, 101, 78, 160, 182, 27, 44, 26, 243, 115, 97, 234, 109, 222, 88, 235, 117, 141, 147, 240, 99, 43, 195, 249, 3, 33, 0, 70, 127, 246, 236, 242, 22, 249, 39, 135, 30, 28, 206, 172, 87, 201, 63, 12, 140, 27, 53, 170, 175, 126, 124, 46, 81, 119, 174, 95, 72, 77, 2, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 138, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}