Transaction Details
Tx hash
befb80c4fb082c1eae4d02af3fa882a898e95620d67a8a04e44a910fb84ee957
Tx prefix hash
4608f0d65d02561f73e3d6dfd391c5eb818385405bde5a968788c6fe85c06f55
Tx public key
343fd55635df82a0269ef0f1870532e192e4ab21837b6b8e0fab6ad6a30a0c5f
Age [y:d:h:m:s]
05:051:19:39:21
Timestamp [UCT] (epoch)
2019-10-11 19:33:06 (1570822386)
Block
283417 (1318630 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01343fd55635df82a0269ef0f1870532e192e4ab21837b6b8e0fab6ad6a30a0c5f021100000011739b3aa9000000000000000000032100e51c2a78a046ec9c61f058c7f412ec83ed1d70cb67f0cb438e85f7c4315b37f0
Outputs
1 output(s) for total of 20.095232505 ARQ
stealth address amount amount idx
00: d4f589fe8aa26a16076bc0d8086af3eb63b1c574744d418b57ffa70b922ccfef 20.095232505 1276907 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": 283435, 
  "vin": [ {
      "gen": {
        "height": 283417
      }
    }
  ], 
  "vout": [ {
      "amount": 20095232505, 
      "target": {
        "key": "d4f589fe8aa26a16076bc0d8086af3eb63b1c574744d418b57ffa70b922ccfef"
      }
    }
  ], 
  "extra": [ 1, 52, 63, 213, 86, 53, 223, 130, 160, 38, 158, 240, 241, 135, 5, 50, 225, 146, 228, 171, 33, 131, 123, 107, 142, 15, 171, 106, 214, 163, 10, 12, 95, 2, 17, 0, 0, 0, 17, 115, 155, 58, 169, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 229, 28, 42, 120, 160, 70, 236, 156, 97, 240, 88, 199, 244, 18, 236, 131, 237, 29, 112, 203, 103, 240, 203, 67, 142, 133, 247, 196, 49, 91, 55, 240
  ], 
  "rct_signatures": {
    "type": 0
  }
}