As I told you in
the other thread, 2xoin's tool is correct. But if you want to construct the r, s and z values by yourself, there is a helpful guide in the linked thread at
http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bitcoin.html?m=1 . All you have to do is extract the scriptSig for each input of the raw transaction (your life is made easier by converting the raw transaction to JSON first).
The scriptSig is a DER signature as you can see, and it has a particular format. In this case,
sequence (which we don't need),
integer and
integer. The last two are the r and s values (the picture calls them x and y), but first you have to "pop" the sequence number out of the DER using e.g
ecdsa.der.remove_sequence(input) in Python. Then you pop r and s using two
ecdsa.der.remove_integer calls, and this'll give you r and s as base10 numbers.
Then the z value is just a double SHA256 of the transaction bytes after performing a little cosmetic surgery on it to add some bytes and substitute in a Ripemd160 hash (see
this code for details).
Obviously then you convert them to hex to match what the SAGE and Python scripts and 2xoin's tool are displaying.
But if you want something quick and dirty (and you probably do), use the 2xoin page or
https://github.com/stateactor/Bitcoin-Key-Compression-Tool . Be warned that the latter was coded to only get r s z for the first input of a raw transaction.
