Transaction Details
Tx hash
aa476039facd40b3af2c438dbe8f27ea8a3724bdd53452d1f22965abb352d07f
Tx prefix hash
908e8c5e112cd2602ecf9508ded430c3eb03bbbd9e73806e232d10fef941f87e
Tx public key
6c6da14341004d747b7a5ee2843eca2885247444d297b91d6ad225fd8cae0b0f
Age [y:d:h:m:s]
05:308:21:09:54
Timestamp [UCT] (epoch)
2019-01-26 00:32:33 (1548462753)
Block
98798 (1502036 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016c6da14341004d747b7a5ee2843eca2885247444d297b91d6ad225fd8cae0b0f032100ba582cbff8739d9887410cb0ad62319944d4ee61b745a5e46fa72252271de50d021b0000000000000000000000000039a3caf700000000000000000000
Outputs
1 output(s) for total of 19.333216231 ARQ
stealth address amount amount idx
00: 0a4e02334a10f7efcc0e9b2b43dd9bd1b7537ddfb12d56a591278d779128f5b5 19.333216231 488060 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": 98816, 
  "vin": [ {
      "gen": {
        "height": 98798
      }
    }
  ], 
  "vout": [ {
      "amount": 19333216231, 
      "target": {
        "key": "0a4e02334a10f7efcc0e9b2b43dd9bd1b7537ddfb12d56a591278d779128f5b5"
      }
    }
  ], 
  "extra": [ 1, 108, 109, 161, 67, 65, 0, 77, 116, 123, 122, 94, 226, 132, 62, 202, 40, 133, 36, 116, 68, 210, 151, 185, 29, 106, 210, 37, 253, 140, 174, 11, 15, 3, 33, 0, 186, 88, 44, 191, 248, 115, 157, 152, 135, 65, 12, 176, 173, 98, 49, 153, 68, 212, 238, 97, 183, 69, 165, 228, 111, 167, 34, 82, 39, 29, 229, 13, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 57, 163, 202, 247, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}