Bitcoin Transaction
40dd3d863258f291b49f51ea2c5a7bee593c692ea2afd6c0b945c9d0222305eb
WARNING: This transaction had an attempted double-spent by
070150d0212dedb85c60c179892e25e…,
but was still confirmed.
Data Embedded in Transaction with Unknown Protocol
(what's this?)
Hex: 58325b7751e00b383217e79f2cbd939e7988d7031d0c69c2404756ce09e0d3dc6567dc21df13d58dde65a62e8773d04d33134950a57f5c426809ca24687a0e1126ace6000b13890055000b0ecc003d2b
-
Amount Transacted
0.25157029 BTC -
Fees
0.00020645 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.