Transaction Details
Tx hash
7d8d05b11a1a11a9dd42ef9781200138d53a5d86ad2f3a9e4f76e2bcae8b4d75
Tx prefix hash
41f9cad4c95e8f0b7ae55204f84ab672ced2e9c3a03adb4cf402d5f4c84e3840
Tx public key
1923a91a4c9a8bc06dc387218bcd1b9d3fc920942518e517446a09f9b3dc5307
Age [y:d:h:m:s]
05:108:16:48:06
Timestamp [UCT] (epoch)
2019-08-11 23:54:22 (1565567662)
Block
240329 (1358958 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011923a91a4c9a8bc06dc387218bcd1b9d3fc920942518e517446a09f9b3dc5307032100d71ddf785e5929a790ba51c6b1ae4163fd987c46ea6cbeb706de76ccad5c93a1021b0000000000000000000000000c1a1522be00000000000000000000
Outputs
1 output(s) for total of 18.071365186 ARQ
stealth address amount amount idx
00: d4b66ffa3432eac03fca1c6b4f6e9474258a6512d460072dd27fd63dd60c4230 18.071365186 1096809 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": 240347, 
  "vin": [ {
      "gen": {
        "height": 240329
      }
    }
  ], 
  "vout": [ {
      "amount": 18071365186, 
      "target": {
        "key": "d4b66ffa3432eac03fca1c6b4f6e9474258a6512d460072dd27fd63dd60c4230"
      }
    }
  ], 
  "extra": [ 1, 25, 35, 169, 26, 76, 154, 139, 192, 109, 195, 135, 33, 139, 205, 27, 157, 63, 201, 32, 148, 37, 24, 229, 23, 68, 106, 9, 249, 179, 220, 83, 7, 3, 33, 0, 215, 29, 223, 120, 94, 89, 41, 167, 144, 186, 81, 198, 177, 174, 65, 99, 253, 152, 124, 70, 234, 108, 190, 183, 6, 222, 118, 204, 173, 92, 147, 161, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 12, 26, 21, 34, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}