Transaction Details
Tx hash
452e05d0039953a00e2fa1d74fd8ce37bb2a0c4f00afb93e21eb976dab149c00
Tx prefix hash
de5268eca1958f9417667bda44b86147d71bebf09ce542a3a73bac753ff3106d
Tx public key
75f739cb430185dd4785160049bf71e5c3403bc2b48dcc5da9c1e102e376098e
Age [y:d:h:m:s]
05:123:08:58:10
Timestamp [UCT] (epoch)
2019-07-27 22:29:23 (1564266563)
Block
229548 (1369464 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0175f739cb430185dd4785160049bf71e5c3403bc2b48dcc5da9c1e102e376098e0321007b4fe07b856bed4bffb01b70c5fad03ae53d83e4cf210de18dd4acac5da4050a021b00000000000000000000000005aa3771c800000000000000000000
Outputs
1 output(s) for total of 18.164505348 ARQ
stealth address amount amount idx
00: cf95d31660dc8f5db3c5683b2bb1be3aad09928c6d1f3c3ee9b85150a4469b41 18.164505348 1071387 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": 229566, 
  "vin": [ {
      "gen": {
        "height": 229548
      }
    }
  ], 
  "vout": [ {
      "amount": 18164505348, 
      "target": {
        "key": "cf95d31660dc8f5db3c5683b2bb1be3aad09928c6d1f3c3ee9b85150a4469b41"
      }
    }
  ], 
  "extra": [ 1, 117, 247, 57, 203, 67, 1, 133, 221, 71, 133, 22, 0, 73, 191, 113, 229, 195, 64, 59, 194, 180, 141, 204, 93, 169, 193, 225, 2, 227, 118, 9, 142, 3, 33, 0, 123, 79, 224, 123, 133, 107, 237, 75, 255, 176, 27, 112, 197, 250, 208, 58, 229, 61, 131, 228, 207, 33, 13, 225, 141, 212, 172, 172, 93, 164, 5, 10, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 170, 55, 113, 200, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}