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