Transaction

e383d3ec9edccf5dc045cf1d91ea08be02cab4fc638de4e5ae98650948da5d56
Timestamp (utc)
2024-03-24 01:17:26
Fee Paid
0.00000015 BSV
(
0.02078676 BSV
-
0.02078661 BSV
)
Fee Rate
10.51 sat/KB
Version
1
Confirmations
101,306
Size Stats
1,426 B

2 Outputs

Total Output:
0.02078661 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM•<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=795.msg8941#msg8941">Quote from: jgarzik on August 12, 2010, 11:39:12 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=795.msg8920#msg8920">Quote from: satoshi on August 12, 2010, 09:20:31 PM</a></div><div class="quote">-paytxfee switch, e.g. -paytxfee=0.01<br/></div><br/>So, -paytxfee sets nTransactionFee.<br/><br/>Can someone explain how nTransactionFee causes a client to behave?<br/><br/>And more specifically, what happens when node A sets 1000.0 and all other nodes use 0.01?<br/><br/><br/></div><br/>From what I understand a node will not include transactions in it's blocks unless the transaction includes a fee that meets the node's requirements. So in the case of a node setting the fee to 1,000 it would likely never include any transactions in blocks it generates, which means it will miss out on any transaction fees other nodes would have gotten. There really isn't a reason to set a nodes requirements higher then the rest of the network since you are basically just pricing yourself out of the market.</div> text/html
    https://whatsonchain.com/tx/e383d3ec9edccf5dc045cf1d91ea08be02cab4fc638de4e5ae98650948da5d56