Transaction Details
Tx hash
4ab7f04c040a6fb569ec94fa5e3dfebaf3a08aa0e39b58b26ed3c293597d138a
Tx prefix hash
56e8284b445c92f7d2d5fa5965bcf32be2c1d4717e3b9ea78c09d522e0286c2d
Tx public key
ad9bca6e2e82db038d6c73b6b9b2d509a3c555a598e9658595fd8ad78ce06d5d
Age [y:d:h:m:s]
05:146:00:49:40
Timestamp [UCT] (epoch)
2019-05-11 17:34:48 (1557596088)
Block
174246 (1386319 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01ad9bca6e2e82db038d6c73b6b9b2d509a3c555a598e9658595fd8ad78ce06d5d032100515d6a564747ef2342a2688b4758b222bfd64f50d1e3f47464a5eb1a62772b2a021b000000000000000000000000018501d3b100000000000000000000
Outputs
1 output(s) for total of 18.650039967 ARQ
stealth address amount amount idx
00: 1b4d3efc204db1e07ad3b045b19476d988e90e96b9d53942480f45a813ef8d1f 18.650039967 788544 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": 174264, 
  "vin": [ {
      "gen": {
        "height": 174246
      }
    }
  ], 
  "vout": [ {
      "amount": 18650039967, 
      "target": {
        "key": "1b4d3efc204db1e07ad3b045b19476d988e90e96b9d53942480f45a813ef8d1f"
      }
    }
  ], 
  "extra": [ 1, 173, 155, 202, 110, 46, 130, 219, 3, 141, 108, 115, 182, 185, 178, 213, 9, 163, 197, 85, 165, 152, 233, 101, 133, 149, 253, 138, 215, 140, 224, 109, 93, 3, 33, 0, 81, 93, 106, 86, 71, 71, 239, 35, 66, 162, 104, 139, 71, 88, 178, 34, 191, 214, 79, 80, 209, 227, 244, 116, 100, 165, 235, 26, 98, 119, 43, 42, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 133, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}