The bitcoin was never in your wallet in the first place. Bitcoins don't "go" anywhere. There are simply transactions that get recorded in the blockchain.
If the transaction gets included into the blockchain then it is called confirmed. Then each additional block added to the blockchain after that is considered to be an additional "confirmation". When there are enough blocks stacked on top of the block with your transaction, the transaction is generally considered to be permanent.
Since your transaction is not confirmed yet, the bitcoins are still recorded in the blockchain as belonging to you.
There are two possibilities:
1. Your wallet has forgotten about the confirmed transaction ca1e4dff695a5a2649514ecefc7a14e693ca706ccc2bf1d47a02fdfa67ba848d where it received the 4.84802738 BTC back on April 29. If this has happened, then the rescan will cause the wallet to read through the entire blockchain again to find all the transactions that the wallet has control over. Therefore, it should find that transaction in the blockchain and update the balance that it shows you to include those 4.84802738 BTC.
OR
2. Your wallet still remembers your new unconfirmed transaction that spends the 4.84802738 BTC, but has forgotten that the 2.74802738 BTC output is going to an address that the wallet controls. If this has happened, then you may need to try the zapwallettxes again, or you may need to try the rescan. zapwallettxes should cause the wallet to forget about the unconfirmed transaction and search the blockchain to find the transaction that paid you, but perhaps for some reason it failed to do that.
If neither zapwallettxes nor rescan fix your problem, then there may be something wrong with the wallet. You'll then need to find the private key for the 1Fnpr866zeRb24maVTtj6Kq162FgKy3c5B address and import that private key into some other wallet that is working properly. The new wallet should then re-scan the blockchain and find the balance that you control.
