Transaction Details
Tx hash
9c7b9f304fcb3320fe8cec7e086db1af39c0a472f8da0d1a2986ee8986be45e2
Tx prefix hash
aa9a04169b55fc5bed7589267f8d1bacf2609e59aea2f1e4b7b37b7e0310097a
Tx public key
d7f61c7c51dcb6467fc5e8d8195424df63acf7ecc911def67df47a5a117d8bfb
Age [y:d:h:m:s]
05:111:22:23:51
Timestamp [UCT] (epoch)
2019-08-10 00:24:36 (1565396676)
Block
238937 (1361230 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d7f61c7c51dcb6467fc5e8d8195424df63acf7ecc911def67df47a5a117d8bfb032100c79e6676bbfa20ad9270baf39b025b3be3bf7a7b3a811def9e173c7af6051220021b0000000000000000000000000444fd0e1700000000000000000000
Outputs
1 output(s) for total of 18.083364172 ARQ
stealth address amount amount idx
00: f6c015fff4327daf215785303245a0f3bc76d3d06bda79cde986f50f4287ac8b 18.083364172 1093946 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": 238955, 
  "vin": [ {
      "gen": {
        "height": 238937
      }
    }
  ], 
  "vout": [ {
      "amount": 18083364172, 
      "target": {
        "key": "f6c015fff4327daf215785303245a0f3bc76d3d06bda79cde986f50f4287ac8b"
      }
    }
  ], 
  "extra": [ 1, 215, 246, 28, 124, 81, 220, 182, 70, 127, 197, 232, 216, 25, 84, 36, 223, 99, 172, 247, 236, 201, 17, 222, 246, 125, 244, 122, 90, 17, 125, 139, 251, 3, 33, 0, 199, 158, 102, 118, 187, 250, 32, 173, 146, 112, 186, 243, 155, 2, 91, 59, 227, 191, 122, 123, 58, 129, 29, 239, 158, 23, 60, 122, 246, 5, 18, 32, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 68, 253, 14, 23, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}