Bitcoin Transaction
bd7a9def0a7bdc792db9afe5bfc508a6168cc2e06818fc12467b65ef6dc5355b
WARNING: This transaction had an attempted double-spent by
2f21a53471eb0d40fb4092e69de2d88…,
but was still confirmed.
Data Embedded in Transaction with Unknown Protocol
(what's this?)
Hex: 58325b7bbab5fafd614b2b8a17a83b8d192167a6b19becec5db3c22e2124a4d6a1ace10865522ae7eb52bca3b212b4ea0774ff20ad566b418d19c6c11d5b19a207aea7000c6a7e0113000c6a6a00024c
-
Amount Transacted
0.46527196 BTC -
Fees
0.00157851 BTC -
Received
-
Confirmations
6+
Details
1 Input Consumed
4 Outputs Created
0.0 BTC
Null Data Transaction
Estimated Value Sent : 0.0015 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.