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