Re: List of all Bitcoin addresses ever used - currently available on temp location

Quote from: MrFreeDragon on January 28, 2021, 03:37:37 PM

And the public key will be the following part:
48304502200a30a8634f41dbd92c007f937f6b0f220cc1f5a321252cc459092e45b1c5377802210 0caace1a19e1d195e8510ac290c13863f4ada16c2837d6af80ea6b237ba65975c01410418a808ea3fc6fd99c11b51f572d2e85b25a33048de2c0afda336c32da4619897629943638def6 df1ab0d3acd35faa7e8c73ff1fc275677f82191b253a7bbf383

So if I take these inputs as an example:

Code:

block_id transaction_hash index time value value_usd recipient type script_hex is_from_coinbase is_spendable spending_block_id spending_transaction_hash spending_index spending_time spending_value_usd spending_sequence spending_signature_hex spending_witness lifespan cdd
66558 d9ff0a82399ae55ab95093020ed6f17bab80697dcafe74d264900cdd56f8c0aa 0 2010-07-13 09:19:38 4000000000 0.4 12Y4RVpkQ4uKCNUpea4jJRWgd2nxScNkaG pubkeyhash 76a91410d7e0a01323508f1881407713971fab34b7898788ac 0 -1 113331 c0ef633ac227c17860abeed2ebbbcfedf4a108e61d9950c0c68171e20e32e945 0 2011-03-13 00:06:05 36 4294967295 48304502200a30a8634f41dbd92c007f937f6b0f220cc1f5a321252cc459092e45b1c53778022100caace1a19e1d195e8510ac290c13863f4ada16c2837d6af80ea6b237ba65975c01410418a808ea3fc6fd99c11b51f572d2e85b25a33048de2c0afda336c32da4619897629943638def6df1ab0d3acd35faa7e8c73ff1fc275677f82191b253a7bbf383 20961987 9704.62361111111
112995 523f57581390203da2aef169b543fc1ddcd84be6dd35cfb248228b0912dc97e3 0 2011-03-10 09:08:48 5001000000 42.5085 1GEX1ZHu5aHjnL6HogKYHfqCAFQvcVWpKA pubkey 4104a2032ae7a01f69747fac92c9c343ce5f1c841d450ada9b9498e84050de80a3e72d7d5f92967c2b1edc061222a28eee5d0256d60b5eafaf8b33e358c6dafa3923ac 1 1 113331 b25bacedd7ecc2d945e69cfe40dade836d57edf7583da70952ee37743d3852a8 0 2011-03-13 00:06:05 45.009 4294967295 483045022100a66be0435ed532f7a065073e2549f6cb13a546efc7f55d49072f5038d0764df502206f426bff777dd44ccbab703541a38d8ff86ae09e350862c8fb9cb2b0dd79c5e801 226637 131.18190243055554

The part I'm looking for is:

Code:

type spending_signature_hex
pubkeyhash 48304502200a30a8634f41dbd92c007f937f6b0f220cc1f5a321252cc459092e45b1c53778022100caace1a19e1d195e8510ac290c13863f4ada16c2837d6af80ea6b237ba65975c01410418a808ea3fc6fd99c11b51f572d2e85b25a33048de2c0afda336c32da4619897629943638def6df1ab0d3acd35faa7e8c73ff1fc275677f82191b253a7bbf383
pubkey 483045022100a66be0435ed532f7a065073e2549f6cb13a546efc7f55d49072f5038d0764df502206f426bff777dd44ccbab703541a38d8ff86ae09e350862c8fb9cb2b0dd79c5e801

If type is pubkeyhash, you want the whole spending_signature_hex (146 characters)
If type is pubkey, you want the last 130 characters? How do I decide where to cut it?