Fee calculator.Four priorities, priced live.

What a Monero transaction costs right now, from the fee estimate of our own node — in XMR and in dollars.

Typical transactions, right now

What wallets would charge

Fee by transaction shape and priority
ShapeLowNormalElevatedPriority
1 in · 2 out
1,536 B
0.00003
$0.0163
0.000122
$0.0652
0.000491
$0.2606
0.006144
$3.26
2 in · 2 out
2,215 B
0.000044
$0.0235
0.000177
$0.0940
0.000708
$0.3758
0.00886
$4.70
4 in · 2 out
3,573 B
0.000071
$0.0379
0.000285
$0.1516
0.001143
$0.6062
0.014292
$7.58
1 in · 16 out
6,253 B
0.000125
$0.0663
0.0005
$0.2652
0.002
$1.06
0.025012
$13.26

Rates per byte from get_fee_estimate: 20 nXMR · 80 nXMR · 320 nXMR · 4,000 nXMR. Fees are rounded up to 0.00000001 XMR. USD at $530.20 per XMR (CoinGecko).

Your transaction

Estimated weight: 1,536 bytes

Low0.00003072 XMR · $0.0163
Normal0.00012288 XMR · $0.0652
Elevated0.00049152 XMR · $0.2606
Priority0.006144 XMR · $3.26
The formula
fee = ceil(weight × rate[priority] / mask) × mask

The node recomputes the four rates from the median block weight and the block reward. See how full blocks are right now on the mempool page.

Questions

How is a Monero fee calculated?

A wallet multiplies the transaction's weight in bytes by a per-byte rate and rounds the result up to a multiple of the quantization mask. The node publishes four rates, one per priority, through get_fee_estimate; the rates follow the recent median block weight and the block reward.

What are the four Monero fee priorities?

Low (unimportant), Normal, Elevated and Priority — priority 1 to 4 in monero-wallet-cli. A higher priority pays a higher rate per byte, so miners pick the transaction first when blocks are full. When blocks are not full, the lowest priority is mined just as quickly.

Why does a transaction with more inputs cost more?

Each input carries a ring of 16 members and its own signature, which adds roughly 700 bytes. The fee is charged per byte, so spending many small coins at once costs more than spending one large coin.

Where do the transaction weights come from?

From the same estimator the reference wallet runs before it sets a fee (wallet2 estimate_tx_weight, with ring size 16, Bulletproofs+, CLSAG and view tags). A real transaction can differ by a few bytes, for example when its extra field is larger.