script – Why are signatures different for inputs from the same address in a single Bitcoin transaction?

I’ve been studying Bitcoin transaction signatures and have noticed some interesting patterns when analyzing transactions containing the same address in different contexts. Here are my observations:

Case 1: Same address, two different transactions (T1 and T2)

As expected, for two separate transactions same addressI have observed the following witness data:

30450221008dbd2c3c33413a58d0217897daa9cfe75a7aaad3d80d915ed74dbfbc7dc70d 43022034a8328a99065ff8f47acb9da4ce213ee6bf90448580cfd5129e36f39a985c3801 023b6bdc0869a329e9d0cb036257eff362aeab11512668090746bf31647a42039e

3045022100cc584f8b3c0a23d5531d1e46b15e10be7138409c46c04a16716af89ea8a653 ec02202a1e364f7c2b0f4f6e995bf73b65a4ed86e5166f9c7544a397a6c38b8db4a43301 023b6bdc0869a329e9d0cb036257eff362aeab11512668090746bf31647a42039e

Here I assume/guess the following:

1. that The first hexadecimal string of the witness is the signature.and
2. that The second hexadecimal string is the public key..

As expected:

1. that the signature is different This is because each signature is associated with a specific transaction.
2. that The public key is the same Because it matches the address.

This makes sense because the signature creation process involves transaction data (or its hash)… but:

Case 2: Transaction with two inputs from the same address (T3)

When analyzing a single transaction with two inputs, both same addressI have observed the following witness data:

30450221008dbd2c3c33413a58d0217897daa9cfe75a7aaad3d80d915ed74dbfbc7dc70d 43022034a8328a99065ff8f47acb9da4ce213ee6bf90448580cfd5129e36f39a985c3801 023b6bdc0869a329e9d0cb036257eff362aeab11512668090746bf31647a42039e

3045022100cc584f8b3c0a23d5531d1e46b15e10be7138409c46c04a16716af89ea8a653 ec02202a1e364f7c2b0f4f6e995bf73b65a4ed86e5166f9c7544a397a6c38b8db4a43301 023b6bdc0869a329e9d0cb036257eff362aeab11512668090746bf31647a42039e

In this case:

1. that the signature is differentThis is true even if both inputs come from the same address.
2. that public key is the same For both inputs, as expected.

This means that the signature is applied to each input individually, rather than to the entire transaction. Each input seems to sign a specific “message”.

question:

1. Why are signatures different for different inputs within the same transaction?
2. Does this mean that the signature is not generated for the entire transaction, but rather for each input independently?
3. What exactly is signed on each input, and what role do UTXOs play in this process? Does your signature have a reference to a specific UTXO?
4. Why is witness data expressed only in hexadecimal binary? A converter for “human” script instructions could not be found. Is it there?
5. Is it correct to say that basically for the same address the locking script will be the same but the unlocking script (witness) will be different because it depends on that specific single input of the transaction?

I would appreciate a clear explanation of this behavior and the underlying mechanism. thank you!