Transaction Details
Tx hash
6a83508e210bc1ab63b5c0dc41285e2f46634099adaf4cccd57d7443dd16338b
Tx prefix hash
dcd679262af5ffe8925095f487e25288f1d30782bc2e89fb44ac96c0ef1fdb3d
Tx public key
cc97e8339730e991e60ce6773ddc182e0be0059fbaffff112c77a167f8fd314d
Age [y:d:h:m:s]
05:307:08:01:06
Timestamp [UCT] (epoch)
2019-01-27 00:17:21 (1548548241)
Block
99503 (1500951 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01cc97e8339730e991e60ce6773ddc182e0be0059fbaffff112c77a167f8fd314d03210097c6f40c05b3ba7ce21b34fac796d10a43cef1c63532f7feb238e1e200f30ece021b0000000000000000000000000006692ec600000000000000000000
Outputs
1 output(s) for total of 19.326547848 ARQ
stealth address amount amount idx
00: 44527d0c6643736176c35635fa8705970773c4cb327d1ebfb6a1568acec323a0 19.326547848 491723 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": 99521, 
  "vin": [ {
      "gen": {
        "height": 99503
      }
    }
  ], 
  "vout": [ {
      "amount": 19326547848, 
      "target": {
        "key": "44527d0c6643736176c35635fa8705970773c4cb327d1ebfb6a1568acec323a0"
      }
    }
  ], 
  "extra": [ 1, 204, 151, 232, 51, 151, 48, 233, 145, 230, 12, 230, 119, 61, 220, 24, 46, 11, 224, 5, 159, 186, 255, 255, 17, 44, 119, 161, 103, 248, 253, 49, 77, 3, 33, 0, 151, 198, 244, 12, 5, 179, 186, 124, 226, 27, 52, 250, 199, 150, 209, 10, 67, 206, 241, 198, 53, 50, 247, 254, 178, 56, 225, 226, 0, 243, 14, 206, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 105, 46, 198, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}