Transaction Details
Tx hash
f74229335bfe8d22a6eb2fedd5bef8ffd918fc1eae1658105873f46921c8b12d
Tx prefix hash
27a6d3cf46065c31adeaa44e0ca6173e5c5d4624e8c94e9012754518b2c47f30
Tx public key
dde4bf31879b5cf3a4024e9187ed56bf0f171dffe9e03bb56d2f6395c256bae6
Age [y:d:h:m:s]
05:270:01:25:52
Timestamp [UCT] (epoch)
2019-01-10 15:02:18 (1547132538)
Block
87843 (1474720 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01dde4bf31879b5cf3a4024e9187ed56bf0f171dffe9e03bb56d2f6395c256bae60321005e75a94711cbef68f0486dcba24a47eb97eb0fb88d009dd99ee87989a03ac56e021b000000000000000000000000001dc9579800000000000000000000
Outputs
1 output(s) for total of 19.434347911 ARQ
stealth address amount amount idx
00: f81767f095778be39644cfff0472198e4aeabc2dbc27b64bbb6c10f0bbbd32ee 19.434347911 433859 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": 87861, 
  "vin": [ {
      "gen": {
        "height": 87843
      }
    }
  ], 
  "vout": [ {
      "amount": 19434347911, 
      "target": {
        "key": "f81767f095778be39644cfff0472198e4aeabc2dbc27b64bbb6c10f0bbbd32ee"
      }
    }
  ], 
  "extra": [ 1, 221, 228, 191, 49, 135, 155, 92, 243, 164, 2, 78, 145, 135, 237, 86, 191, 15, 23, 29, 255, 233, 224, 59, 181, 109, 47, 99, 149, 194, 86, 186, 230, 3, 33, 0, 94, 117, 169, 71, 17, 203, 239, 104, 240, 72, 109, 203, 162, 74, 71, 235, 151, 235, 15, 184, 141, 0, 157, 217, 158, 232, 121, 137, 160, 58, 197, 110, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 29, 201, 87, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}