Timeline for processing input tx in bitcoin's block response and obtain transaction value of each input
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2023 at 10:31 | comment | added | dassd | @MonteConte The output contains the amount of satoshis that are locked with the scriptPubKey (say 1,000,000). When the input offers the correct scriptSig, all satoshis (all 1,000,000 satoshis) from the referenced output are unlocked. However, that amount is not written anywhere in the input. To see how much is being spent, it is necessary to look at the referenced transaction and output. Block explorers do the same when they show how many bitcoins are spent/taken with some input. | |
| Oct 23, 2023 at 9:09 | comment | added | Monte Conte |
thanks for answer, can you explain more on this : To see exactly what that amount is, you need to look at the referenced transaction and the referenced output in it. thats my script sig that i specified and i get pubkey of destination on tx_out which can be translated to dest address. but all block explorers have the source destination, how they take it? i'm trying to use bitcoin protocol to take them, not APIs.
|
|
| Oct 23, 2023 at 5:28 | vote | accept | Monte Conte | ||
| Oct 22, 2023 at 21:39 | history | edited | dassd | CC BY-SA 4.0 |
added 381 characters in body
|
| Oct 22, 2023 at 21:19 | history | edited | dassd | CC BY-SA 4.0 |
added 63 characters in body
|
| Oct 22, 2023 at 21:05 | history | edited | dassd | CC BY-SA 4.0 |
added 187 characters in body
|
| Oct 22, 2023 at 20:59 | history | answered | dassd | CC BY-SA 4.0 |