Transaction Details
Tx hash
bff7e8e202addf91dddfd306086e62d42173974c20bfa30ef5962a59a6f23dc7
Tx prefix hash
d9959b15e5cdcc5c7a89f32d665dd03888e13303de684bdb2259c991df60e064
Tx public key
be5b20fc6a080adf3558a00138cb057fe59d045d6890fffa849098bfe5267d40
Age [y:d:h:m:s]
05:205:02:29:51
Timestamp [UCT] (epoch)
2019-05-06 11:05:01 (1557140701)
Block
170513 (1427970 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01be5b20fc6a080adf3558a00138cb057fe59d045d6890fffa849098bfe5267d40032100d2e18f34c5e6b2a47cc0998e959dea3c8e6f4657a47dd9b2fa934eb2cdc20667021b000000000000000000000000007d01d3b100000000000000000000
Outputs
1 output(s) for total of 18.683215015 ARQ
stealth address amount amount idx
00: 90b19d6c8a8628833231c96f146ef88555075cf9a2f8532b131ce2c738fa18a9 18.683215015 774705 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": 170531, 
  "vin": [ {
      "gen": {
        "height": 170513
      }
    }
  ], 
  "vout": [ {
      "amount": 18683215015, 
      "target": {
        "key": "90b19d6c8a8628833231c96f146ef88555075cf9a2f8532b131ce2c738fa18a9"
      }
    }
  ], 
  "extra": [ 1, 190, 91, 32, 252, 106, 8, 10, 223, 53, 88, 160, 1, 56, 203, 5, 127, 229, 157, 4, 93, 104, 144, 255, 250, 132, 144, 152, 191, 229, 38, 125, 64, 3, 33, 0, 210, 225, 143, 52, 197, 230, 178, 164, 124, 192, 153, 142, 149, 157, 234, 60, 142, 111, 70, 87, 164, 125, 217, 178, 250, 147, 78, 178, 205, 194, 6, 103, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 125, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}