Transaction Details
Tx hash
51a882500a804e78a001a82731fa6c94e533ed4f11ba69d26fb9373229e5abc7
Tx prefix hash
28650e6c91fd417292f22fd9bc2dc27d9eec1d239773b685c10a7fecc1394611
Tx public key
d22d77b17fd0c4dc4321f9e6b9a1bb27d994b3b0052f80e4b00bdc6ec6b09ad5
Age [y:d:h:m:s]
05:239:17:01:31
Timestamp [UCT] (epoch)
2019-04-05 01:19:56 (1554427196)
Block
148051 (1452699 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d22d77b17fd0c4dc4321f9e6b9a1bb27d994b3b0052f80e4b00bdc6ec6b09ad503210077791e2f5b59ec00c9b3337f3584360e40355e362e24c8cb10b4ace63a92669a021b000000000000000000000000000d968e9c00000000000000000000
Outputs
1 output(s) for total of 18.884318010 ARQ
stealth address amount amount idx
00: 9994f73fd4e655843168ec1dc8722627f77f30b76516d4c7f116af781ddedf39 18.884318010 679254 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": 148069, 
  "vin": [ {
      "gen": {
        "height": 148051
      }
    }
  ], 
  "vout": [ {
      "amount": 18884318010, 
      "target": {
        "key": "9994f73fd4e655843168ec1dc8722627f77f30b76516d4c7f116af781ddedf39"
      }
    }
  ], 
  "extra": [ 1, 210, 45, 119, 177, 127, 208, 196, 220, 67, 33, 249, 230, 185, 161, 187, 39, 217, 148, 179, 176, 5, 47, 128, 228, 176, 11, 220, 110, 198, 176, 154, 213, 3, 33, 0, 119, 121, 30, 47, 91, 89, 236, 0, 201, 179, 51, 127, 53, 132, 54, 14, 64, 53, 94, 54, 46, 36, 200, 203, 16, 180, 172, 230, 58, 146, 102, 154, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 13, 150, 142, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}