Previous outputs which this transaction is spending weren't "scripthash", they were Pay To Witness Pubkey Hash[1]. That is why the signature (or more precisely the scriptsig) is "transferred" elsewhere in a field called "witness" instead of it being in its usual place after the outpoint.
[1]
https://bitcoin.stackexchange.com/questions/64733/what-is-p2pk-p2pkh-p2sh-p2wpkh-eli5"txinwitness": [ "30450221009c081fce7e263de3c8a0b0b12b18b6338cb2db4fc2f37ce3d22ec4ad618d611002205 21e0fbabb810593ef6878169e0d1020e69b167b9bbf54915b44e92c5b55ab7301",
"210279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798ac"
],
This is your scriptsig.
30 <-Sequence tag of DER
45 <-DER length
02 <-Int tag of DER
21 <-DER Length
009c081fce7e263de3c8a0b0b12b18b6338cb2db4fc2f37ce3d22ec4ad618d6110 <-x coordinate of R
02 <-Int tag of DER
20 <-DER Length
521e0fbabb810593ef6878169e0d1020e69b167b9bbf54915b44e92c5b55ab73 <-s
01 <-SigHashType
21 <-OP_PushData
0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798ac <-compressed public key
(there are some CompactInt sizes among these numbers that the JSON serialization has omitted though)
