Transaction Details
Tx hash
4e2d01ce4e21d63fe2acd787170df52e02ab49d7c468439e066a657f1b1dcc78
Tx prefix hash
16e9e554f15d9841e8e9a5e821d867e9e7d51e3fc3414a615b6cf0457eab2c0f
Tx public key
0be6fd60f9b56fbe87280c1517c07a14f88a2dbc5866d9b0ee83fe1562e63cb8
Age [y:d:h:m:s]
05:326:04:55:16
Timestamp [UCT] (epoch)
2019-01-04 08:35:11 (1546590911)
Block
83386 (1514371 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010be6fd60f9b56fbe87280c1517c07a14f88a2dbc5866d9b0ee83fe1562e63cb8032100233a2d2496551fda7f9c6a3bcaa344acc8e31e335d70676de6e8e9c27d8ef53b021b0000000000000000000000000009b8e05600000000000000000000
Outputs
1 output(s) for total of 19.475694907 ARQ
stealth address amount amount idx
00: bc9004fba3e3a4ee2da6cbbeae3959813cc0787e3f4d7d2e45fb0e61be9d1c19 19.475694907 413333 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": 83404, 
  "vin": [ {
      "gen": {
        "height": 83386
      }
    }
  ], 
  "vout": [ {
      "amount": 19475694907, 
      "target": {
        "key": "bc9004fba3e3a4ee2da6cbbeae3959813cc0787e3f4d7d2e45fb0e61be9d1c19"
      }
    }
  ], 
  "extra": [ 1, 11, 230, 253, 96, 249, 181, 111, 190, 135, 40, 12, 21, 23, 192, 122, 20, 248, 138, 45, 188, 88, 102, 217, 176, 238, 131, 254, 21, 98, 230, 60, 184, 3, 33, 0, 35, 58, 45, 36, 150, 85, 31, 218, 127, 156, 106, 59, 202, 163, 68, 172, 200, 227, 30, 51, 93, 112, 103, 109, 230, 232, 233, 194, 125, 142, 245, 59, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 184, 224, 86, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}