Transaction Details
Tx hash
5dcec96c4c9ca99b6b3afdf6634aa278e6c322aaa7b90b7e5b1e23402ea4b5f4
Tx prefix hash
338a710802828e0ec3dc48be637fe70bcfce02b92f9457a9a98f004e08c39c07
Tx public key
fa3fb7f7b2f825c6d38d9d78bc6c12a6841d20874da9d9f1e69fed77f50b4658
Age [y:d:h:m:s]
05:102:19:37:30
Timestamp [UCT] (epoch)
2019-08-19 07:43:57 (1566200637)
Block
245620 (1354687 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01fa3fb7f7b2f825c6d38d9d78bc6c12a6841d20874da9d9f1e69fed77f50b46580321000ea67f17a653da7c018944e44b30e72d79d6a799c6b77e26d291032cbc79e3cf021b00000000000000000000000003fb76922e00000000000000000000
Outputs
1 output(s) for total of 18.025829574 ARQ
stealth address amount amount idx
00: 637b392b684d63c972fdafaa535b9e2673f1cde0ab3fed4404ed240f6e163276 18.025829574 1106136 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": 245638, 
  "vin": [ {
      "gen": {
        "height": 245620
      }
    }
  ], 
  "vout": [ {
      "amount": 18025829574, 
      "target": {
        "key": "637b392b684d63c972fdafaa535b9e2673f1cde0ab3fed4404ed240f6e163276"
      }
    }
  ], 
  "extra": [ 1, 250, 63, 183, 247, 178, 248, 37, 198, 211, 141, 157, 120, 188, 108, 18, 166, 132, 29, 32, 135, 77, 169, 217, 241, 230, 159, 237, 119, 245, 11, 70, 88, 3, 33, 0, 14, 166, 127, 23, 166, 83, 218, 124, 1, 137, 68, 228, 75, 48, 231, 45, 121, 214, 167, 153, 198, 183, 126, 38, 210, 145, 3, 44, 188, 121, 227, 207, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 251, 118, 146, 46, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}