ECDSA Signature and the “z” value

from above link learn calculation of z value and to get private key


transaction you get

R = d47ce4c025c35ec440bc81d99834a624875161a26bf56ef7fdc0f5d52f843ad1

S1 = 44e1ff2dfd8102cf7a47c21d5c9fd5701610d04953c6836596b4fe9dd2f53e3e

S2 = 9a5f1c75e461d7ceb1cf3cab9013eb2dc85b6d0da8c3c6e27e3a5a5b3faa5bab

Z1 = c0e2d0a89a348de88fda08211c70d1d7e52ccef2eb9459911bf977d587784c6e

Z2 = 17b0f41c8c337ac1e18c98759e83a8cccbc368dd9d89e5f03cb633c265fd0ddc

z = 7a1a7e52797fc8caaa435d2a4dace39158504bf204fbe19f14dbb427faee50ae

private key = c477f9f65c22cce20657faa5b2d1d8122336f851a508a1ed04e479c34985bf96

but the other transaction not providing corresponding private key

with same identical R value = d47ce4c025c35ec440bc81d99834a624875161a26bf56ef7fdc0f5d52f843ad1








  • Keep in mind that the signs of the S values might have been flipped and you will need to try unflipping them. My answer on another post has an explanation and example code for doing this: bitcoin.stackexchange.com/questions/35848/… Jun 2, 2015 at 16:35
  • Hi again, Prabu. I'm not sure I understand. When I try all of those transactions, I always find the same c477f9... private key (without even needing David Grayson's trick to compensate for tx malleability). Could you be more specific? Jun 2, 2015 at 18:30
  • Hi Christopher Gurnee, your get same private key all transaction can you please explain two of the transaction getting same value in detail step by step like (bitcoin.stackexchange.com/questions/25814/…) Willem Hengeveld
    – Prabu r
    Jun 3, 2015 at 6:27
  • I used the Python code described in this answer and the modified tx utility I mentioned in this comment. Let me know if you'd still like an answer here.... Jun 3, 2015 at 8:22
  • Christopher Gurnee, i try many time other transaction i m not getting same private key , and your mention some Python code there is no r s z getting script thank your help
    – Prabu r
    Jun 8, 2015 at 5:19


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.