Transaction Details
Tx hash
6193c772bd836edd7d6a322eb698ad0e44c5709ae01f34dc33bdf322ce7eb946
Tx prefix hash
160e3b72c8407055725d18c0269c3a49fce3ce8ba96a6617dd91528db7a1c294
Tx public key
7234bc804e815ca7d9c85fb659d695626afaf10184ec988e73602baedfd210dd
Age [y:d:h:m:s]
05:345:19:10:51
Timestamp [UCT] (epoch)
2018-12-22 10:49:37 (1545475777)
Block
74244 (1528212 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
017234bc804e815ca7d9c85fb659d695626afaf10184ec988e73602baedfd210dd032100e7d1c6d821f2b03c90a80e01fdd668cdace8aef91fe1f556074807a57b6f5bd4021b0000000000000000000000000006fa87cd00000000000000000000
Outputs
1 output(s) for total of 19.560787442 ARQ
stealth address amount amount idx
00: 956ea6e903be85acd47074f5ffb399cca8522dd8d72d6aa878f9833792cbbb4d 19.560787442 379179 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": 74262, 
  "vin": [ {
      "gen": {
        "height": 74244
      }
    }
  ], 
  "vout": [ {
      "amount": 19560787442, 
      "target": {
        "key": "956ea6e903be85acd47074f5ffb399cca8522dd8d72d6aa878f9833792cbbb4d"
      }
    }
  ], 
  "extra": [ 1, 114, 52, 188, 128, 78, 129, 92, 167, 217, 200, 95, 182, 89, 214, 149, 98, 106, 250, 241, 1, 132, 236, 152, 142, 115, 96, 43, 174, 223, 210, 16, 221, 3, 33, 0, 231, 209, 198, 216, 33, 242, 176, 60, 144, 168, 14, 1, 253, 214, 104, 205, 172, 232, 174, 249, 31, 225, 245, 86, 7, 72, 7, 165, 123, 111, 91, 212, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 250, 135, 205, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}