transactionfee.info

Check the fee efficiency of your last transaction!
xx
$
sat/byte

This transaction spends SegWit inputs, which results in a smaller transaction vsize and thus lower fees. This transaction does not spend SegWit inputs. Transaction vsize and thus fees could be vastly improved using SegWit.
 
This transaction does not batch outputs. A transaction which batches multiple outputs could be significantly cheaper. The savings are calculated with 20 batched outputs. This transaction batches outputs with one being a change output. Without batching this transaction would create change outputs. These change outputs would need to be spend as an input and thus result in a higher size per transaction.
 
This transaction has X (m-of-n) multisig input. Multisig hotwallets often don't provide more security, but increase the size and thus the fee. This transaction does not spend multisig inputs. Multisig often doesn't provide more security in hot wallets, but increases the size and thus the fee.
 

...it could potentially have saved about in fees
and would be ~ cheaper at current price.
This would be a reduction per user-output.

Scoreboard

SENT FROMTXIDDATE SENTFEE PER BYTECOULD SAVE (%)COULD SAVE ($)at current price
SENT FROM#TX   ▾AVG FEE PER OUTPUTAVG COULD SAVEAVG COULD SAVE OUTPUTAVG OUTPUTSSEGWITBATCHING
SENT FROM#TX   ▾AVG FEE PER OUTPUTAVG COULD SAVEAVG COULD SAVE OUTPUTAVG OUTPUTSSEGWIT

Further Information

Transactions and services or wallets shown here are based on user input. The site-owner is not liable for the correctness of this data.
developed by b10c