Transaction Details
Tx hash
0ebe757e708d272e243385ccc609d7891d04f02be3e4292e35f6311939427ee0
Tx prefix hash
f6da037275252dfa3e5b773e552e25de7a7cce91a76f31f5fd06b7db5152d6a0
Tx public key
bb7a0b81f0a7b8aaee4d28989d7d08035ae1c5a8dc6afb0e12b6f0bec2371ba7
Age [y:d:h:m:s]
05:297:06:23:41
Timestamp [UCT] (epoch)
2019-02-06 09:36:47 (1549445807)
Block
106948 (1493736 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bb7a0b81f0a7b8aaee4d28989d7d08035ae1c5a8dc6afb0e12b6f0bec2371ba7032100514014391c9cefb8fd23ffc5bdff60b8269b5f9fcb585e394a8a3039fcf476c0021b000000000000000000000000001a95959d00000000000000000000
Outputs
1 output(s) for total of 19.258082448 ARQ
stealth address amount amount idx
00: 8494a54fa127351ccf39e278b9d4b11b7f3af237ec012bead23ff0c64f389c6a 19.258082448 525974 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": 106966, 
  "vin": [ {
      "gen": {
        "height": 106948
      }
    }
  ], 
  "vout": [ {
      "amount": 19258082448, 
      "target": {
        "key": "8494a54fa127351ccf39e278b9d4b11b7f3af237ec012bead23ff0c64f389c6a"
      }
    }
  ], 
  "extra": [ 1, 187, 122, 11, 129, 240, 167, 184, 170, 238, 77, 40, 152, 157, 125, 8, 3, 90, 225, 197, 168, 220, 106, 251, 14, 18, 182, 240, 190, 194, 55, 27, 167, 3, 33, 0, 81, 64, 20, 57, 28, 156, 239, 184, 253, 35, 255, 197, 189, 255, 96, 184, 38, 155, 95, 159, 203, 88, 94, 57, 74, 138, 48, 57, 252, 244, 118, 192, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 26, 149, 149, 157, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}