Bitcoin Transaction
032390a01b1e991758d07acd2ce174e04b42ef4f424761d3bfefeee5b5b21820
WARNING: This transaction had an attempted double-spent by
ebb4ab51466fdc02ebbc80810f9bb5b…,
but was still confirmed.
Data Embedded in Transaction with Unknown Protocol
(what's this?)
Hex: 58325be6bb3d5ddd91d0c0702b1d0b6a88e328ff0c429a0da9f2bbe9575f622c676aa75b12292ac7a2b5a30e1efde50f45e1151f6f251b6af0f230a7ad0411246eaed9000b219a001b000b0ecc003d2c
-
Amount Transacted
0.27842014 BTC -
Fees
0.00014351 BTC -
Received
-
Confirmations
6+
Details
1 Input Consumed
4 Outputs Created
0.0 BTC
Null Data Transaction
Estimated Value Sent : 0.0038 BTC (more)
"Estimated Value Sent" excludes known change addresses.
For example, let's say we have a single transaction where address A sends 1 BTC to address B and also 1 BTC back to address A as change, then only 1 BTC is estimated to have been sent.
Proper use of a new change address for each transaction (like all HD wallet implementations) obfuscate this feature.