Transaction Details
Tx hash
b4f1e4c69651236b2ffc7ad44d8c8543c432471764250f4b50b188ab7c5f1706
Tx prefix hash
82aa4343c5405d2f42f91dac26c24919416160b2af063278759092315a9576c8
Tx public key
aed8b71f74fdf22b36fe2f27874c609c2de278970c91056edcbc8bcce8086f99
Age [y:d:h:m:s]
05:327:14:31:51
Timestamp [UCT] (epoch)
2019-01-09 04:49:37 (1547009377)
Block
86812 (1515344 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01aed8b71f74fdf22b36fe2f27874c609c2de278970c91056edcbc8bcce8086f99032100e50cef0aba2a61930129171452b74ba60c6194aed505af07c484212bc409f2d3021b000000000000000000000000002ec9579800000000000000000000
Outputs
1 output(s) for total of 19.443857856 ARQ
stealth address amount amount idx
00: 3e3aeef2e3fcb18252236f1dda3f370d9c057e01cb75a12e78539df4aae65d62 19.443857856 428944 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": 86830, 
  "vin": [ {
      "gen": {
        "height": 86812
      }
    }
  ], 
  "vout": [ {
      "amount": 19443857856, 
      "target": {
        "key": "3e3aeef2e3fcb18252236f1dda3f370d9c057e01cb75a12e78539df4aae65d62"
      }
    }
  ], 
  "extra": [ 1, 174, 216, 183, 31, 116, 253, 242, 43, 54, 254, 47, 39, 135, 76, 96, 156, 45, 226, 120, 151, 12, 145, 5, 110, 220, 188, 139, 204, 232, 8, 111, 153, 3, 33, 0, 229, 12, 239, 10, 186, 42, 97, 147, 1, 41, 23, 20, 82, 183, 75, 166, 12, 97, 148, 174, 213, 5, 175, 7, 196, 132, 33, 43, 196, 9, 242, 211, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 46, 201, 87, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}