Transaction Details
Tx hash
673a4ffb905d777c26f9b83fd6cf0035cb9b4d643da28575a192646d5edf9f35
Tx prefix hash
a7e369076a0a18dda84765d9cbdf713cf02355e29c1509c90f819a40f010224a
Tx public key
69b867ae175d0e14ed804497f9f1542125ea75b655c8d801bea344e7e1225fd2
Age [y:d:h:m:s]
05:104:03:45:15
Timestamp [UCT] (epoch)
2019-06-26 16:48:13 (1561567693)
Block
207056 (1356361 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0169b867ae175d0e14ed804497f9f1542125ea75b655c8d801bea344e7e1225fd2032100f29e4a55d66c41c67fd7d324ed24919bd1be1e0a8d2b7e51785b12e971808d99021b000000000000000000000000005e3fd33900000000000000000000
Outputs
1 output(s) for total of 18.360618444 ARQ
stealth address amount amount idx
00: 0c54b1d3d8cd9ece2a4b09ac6a4d6c0fc4b609e7ea4f22554a5fa0e621785d27 18.360618444 949244 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": 207074, 
  "vin": [ {
      "gen": {
        "height": 207056
      }
    }
  ], 
  "vout": [ {
      "amount": 18360618444, 
      "target": {
        "key": "0c54b1d3d8cd9ece2a4b09ac6a4d6c0fc4b609e7ea4f22554a5fa0e621785d27"
      }
    }
  ], 
  "extra": [ 1, 105, 184, 103, 174, 23, 93, 14, 20, 237, 128, 68, 151, 249, 241, 84, 33, 37, 234, 117, 182, 85, 200, 216, 1, 190, 163, 68, 231, 225, 34, 95, 210, 3, 33, 0, 242, 158, 74, 85, 214, 108, 65, 198, 127, 215, 211, 36, 237, 36, 145, 155, 209, 190, 30, 10, 141, 43, 126, 81, 120, 91, 18, 233, 113, 128, 141, 153, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 94, 63, 211, 57, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}