Wallet SSC: 0.00000000 / $0
Standard Transaction to Bitcoin address step-by-step. P2PKH p2pkh, p2sh, p2wpkh, p2wsh - SecretScan.org

Bitcoin transaction

Standard Transaction to Bitcoin address step-by-step.
Type Legacy and Segwit address -> p2pkh, p2sh, p2wpkh, p2wsh

Creating a new Transaction. The In’s and Out’s of Transactions


version 01000000 Bitcoin version number
input count
01
input output hash Hash of the transaction containing the output we're spending. Reversed automatically.
output index decimal Number transactions. There can be several outputs in the referenced transaction, this identifies which of those outputs we're using (counting from zero). For example 2 = 02000000 (hex and reverse)
script length --- For example: ScriptSig 216 length: 108 bytes, '6c' in hex
scriptSig ScriptSig size | ScriptSig | Hash type | length bytes | Public key
address
amount satoshi (BTC: 0.00000000, 0.00$) Total balance. For Segwit addresses only. To sign a transaction in offline mode, please specify the full amount of the transaction input.
sequence This transaction supports the Replace-By-Fee (RBF) function, which allows you to increase the commission.
output count
01
fees satoshi (BTC: 0.00000000, 0.00$) The fee you will pay for this transaction. Read more below. Example: In the input field, amount = 10000, In the output field, value = 10000 and the checkbox is selected. When fees = 500 is specified, regardless of the value field, the amount there will be 9500.
amount total 0 BTC
output value satoshi (BTC: 0.00000000, 0.00$)
address
script length
---
scriptPubKey
---
block lock time decimal Meaning this transaction was posted after that block. For example block 782987: 8bf20b00 (hex and reverse)
⚠️
does not automatically create change outputs, so you can easily accidentally pay a large transaction fee. Create a multi-output transaction so you can send change to yourself.
* required fields.

The serialized signed transaction is (not broadcast to the Bitcoin Network):
copy
01000000 01 00000000 00 fdffffff 01 0000000000000000 00 00000000
transaction hash
---
size
0 vB
fee (recommended)
0 satoshi
This is the recommended fee calculated in real time. Data from blockchain.info was used
Broadcasting the Raw Transaction Into the Bitcoin Network: blockchair.com mempool.space blockcypher.com etc.
Decoded Transaction: live.blockcypher.com, blockchain.com

Note:

Transaction Fee

Change is given to the original spender if the sum of the inputs is greater than the amount being sent to the recipient. After adding the "change" output, if the sum of the inputs is greater than the sum of the outputs, the remainder is collected by the miner who confirms your transaction, which is called the "fee".

The transaction fee that goes to the miner is the delta between the total input and output amounts. In the example transaction, the miner fee is calculated as:
fee = (input amount) - (spend amount + change amount)
fee = (17373066) - (390582 + 16932484)
fee = 50000 satoshi

Change is given to the original spender if the sum of the inputs is greater than the amount being sent to the recipient. After adding the “change” output, if the sum of the inputs is greater than the sum of the outputs, the remainder is collected by the miner who confirms your transaction, which is called the “fee”. Naturally, the sum of all bitcoins in the inputs must be greater than or equal to the sum of all bitcoins in the outputs, or else your transaction will get rejected.

Replace-by-fee (RBF) Bitcoin

Replace-by-fee (RBF) is a feature that allows users to replace one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee. This can be done multiple times while the transaction is unconfirmed. Transaction replacement

Additional materials

Bitcoin Wiki
Most of this data has been automatically parsed out of the original source code for each cryptocurrency. Still, there exists chance of bugs/error. Please report any errors at: info@secretscan.org Your Private Key is a unique secret number that only you know. It can be encoded in a number of different formats. We show the Public Address and Public Key that corresponds to your Private Key as well as your Private Key in the most popular encoding formats (WIF, HEX).
Our website uses cookies (ie. Cookies) for statistical, advertising and functional. Thanks to them, we can customize the site to your needs. Anyone can accept cookies, or has the ability to disable them in your browser, so you will not collect any information.
Got it