After processing a transaction into consensus, the Hedera network nodes report the results of that transaction in a ‘record’. That record can be retrieved either directly by a query of a mainnet node or via a mirror node.
Amongst other information, a transaction record lists
- the total transaction fee paid
- a list of the net balance changes for any account impacted by the transaction - including the Hedera account 0.0.98 & node accounts (currently accounts 0.003 - 0.0.12) receiving transaction fees
If any one of the accounts had a threshold set that is exceeded by an amount going in or out, then the record will be persisted for 25 hours and not the default 3 minutes. Such a record is referred to as a 'threshold record'.
- the transaction fee total does not include the fee for a threshold record as it might have been the case that it was not the same account paying for the transaction as requested the longer storage.
- if the transaction fails due to insufficient balance in the paying account, then the transaction fee will report what the total fee would have been
- the current model is that the fees for persisting a threshold record for 25 hours are included in the net balance changes for the Hedera account 0.0.98 and whichever account had set the threshold. In the future, we plan to break out these threshold fees for greater clarity.
As an example, if account 0.0.1000 was sending 10,000,000 tinybar to account 0.0.2000, and the fee for this cryptotransfer was 250,000 tinybar, split with 240,000 tinybar going to 0.0.98, and 10,000 tinybar going to the node account 0.0.3 that submitted the transaction, then the transaction record would look like
transaction fee = 250,000
Note that all the transfers sum to zero.