APIs About Classic View

Transaction

09c446196ffea0779de63a77eb12d1092e2263e216f68195990efce21ab6ebbe

0000000000000000000ab0967cb6680e1e98a06a81e38a6278d434590502edf0

Fee Paid

0.00000418 BSV(0.00001306 BSV - 0.00000888 BSV)

Fee Rate

1,017 sat/KB

Confirmations

298,821

Timestamp (utc)

2018-08-19 18:01:22

Version

1

411 B

1 Input

Total Input: 0.00001306 BSV

#0
1DYYKjqz9pAF9V4SGsqCwCVeU5XQdVgYiR
via c20cd6708f71b0a0e9c7152c4ec39acb523821bcd6fa7fb1d7ba79b6989ebfeb [0]
0.00001306 BSV

2 Outputs

Total Output: 0.00000888 BSV

#0
1DYYKjqz9pAF9V4SGsqCwCVeU5XQdVgYiR
spent b5b31bfca201d6538c2061799a53245f334c9c3593f3da6042e7ae9616fd029e [2]
0.00000888 BSV
#1
memo.cash - Post topic message
0 BSV
jmBitcoin CashL¿why not just drop the block-size limit entirely RIGHT NOW? what are the arguments for keeping an arbitrary cap? let the miner just stamp into a block whatever arrives & whatever it can handle
https://whatsonchain.com/tx/09c446196ffea0779de63a77eb12d1092e2263e216f68195990efce21ab6ebbe
jmBitcoin CashL¿why not just drop the block-size limit entirely RIGHT NOW? what are the arguments for keeping an arbitrary cap? let the miner just stamp into a block whatever arrives & whatever it can handle