Transaction Details
Tx hash
be6054b8de3103c8eba72d618a9887e540140180f74b759fdac4ff55bc3216f2
Tx prefix hash
591162b004abd9de06c574d46a039b26f8d1fef6bc42c27030bc27b2b5c8a02a
Tx public key
a8f0324a6911a5c9c3aa81d61eb0574e9baab3610d509f64928198a4e85d0f7e
Age [y:d:h:m:s]
05:122:22:48:21
Timestamp [UCT] (epoch)
2019-07-29 13:36:53 (1564407413)
Block
230715 (1369135 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a8f0324a6911a5c9c3aa81d61eb0574e9baab3610d509f64928198a4e85d0f7e032100edc0d68b3cd85facd6b29a3d15d4c2dc601aa38e92b2fb914bbb5a004720692e021b000000000000000000000000062d7975fa00000000000000000000
Outputs
1 output(s) for total of 18.154400174 ARQ
stealth address amount amount idx
00: f7b8d0dc355c6c2e5ce17e0c29a7fc4aa9d8b47e72b54702dc656b62578f9bc8 18.154400174 1074706 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": 230733, 
  "vin": [ {
      "gen": {
        "height": 230715
      }
    }
  ], 
  "vout": [ {
      "amount": 18154400174, 
      "target": {
        "key": "f7b8d0dc355c6c2e5ce17e0c29a7fc4aa9d8b47e72b54702dc656b62578f9bc8"
      }
    }
  ], 
  "extra": [ 1, 168, 240, 50, 74, 105, 17, 165, 201, 195, 170, 129, 214, 30, 176, 87, 78, 155, 170, 179, 97, 13, 80, 159, 100, 146, 129, 152, 164, 232, 93, 15, 126, 3, 33, 0, 237, 192, 214, 139, 60, 216, 95, 172, 214, 178, 154, 61, 21, 212, 194, 220, 96, 26, 163, 142, 146, 178, 251, 145, 75, 187, 90, 0, 71, 32, 105, 46, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 45, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}