No clue how Construct handles https or shows certain data in the inspector, but by default, the URL is indeed encrypted by the time it leaves the browser to the destination server (which in this case seems to be your local machine).
After receiving the request a secure channel is established between client and server and everything goes through that channel from this point onwards. This is done by asking the DNS server to provide an IP:port mapping for the channel. At no point prior is data sent visible, other than some header information regarding the target, which the DNS reads to point to the destination host.
In order to hide transaction calls from the player, you would need to encrypt the payload on client side and decrypt it on the server. Obfuscating variable names seems to be a poor measure, since ?asda34859=4000000 can be crosschecked with the score the player has made in that session and figure out that asda34859 is the score variable - not to mention development hell to map the obfuscated variables with the real database names.
For starters, you could encode your payload in base64 and split the string in 2-3 variables.