Transaction

c1ba767e8251310d68073d1b7e181a4c6b57ea126a002f965c0f56a6dd046868
Timestamp (utc)
2024-03-30 22:50:59
Fee Paid
0.00000015 BSV
(
0.00079205 BSV
-
0.00079190 BSV
)
Fee Rate
10.52 sat/KB
Version
1
Confirmations
96,218
Size Stats
1,425 B

2 Outputs

Total Output:
0.00079190 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/c1ba767e8251310d68073d1b7e181a4c6b57ea126a002f965c0f56a6dd046868