LTC Address MGVGhxDasUg7zVZKq2gienaTYdgUrDkCkh

6+ confirmations

87c9396ecd4b99eecb7e825efceeeb18a983f673f75b83dc3a296f4721b282e5

2 Inputs Consumed

1.32609442 LTC from
MGVGhxDasUg7zVZKq2gienaTYdgUrDkCkh (output)

208.52041634 LTC from
M8FUHdkmTdU9T35AA9N1kkQCkYKFRXiGfq (output)

2 Outputs Created

2.0 LTC to
Lbrg4PfLvjNK8dyzT4xbFof93ogY4xQq8Y (spent)

207.84583276 LTC to
M8FUHdkmTdU9T35AA9N1kkQCkYKFRXiGfq (spent)

Estimated Value Sent : 2.0 LTC (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.

6+ confirmations

554fe2af4e5255b51c52254d41a8a427a892d3bf9f3057e05d5ab90026681be0

1 Input Consumed

1.43650642 LTC from
MGVGhxDasUg7zVZKq2gienaTYdgUrDkCkh (output)

2 Outputs Created

0.11 LTC to
MDZHWaLCdHSGGXSK9JjEAuVFEd3AU99D2y (spent)

1.32609442 LTC to
MGVGhxDasUg7zVZKq2gienaTYdgUrDkCkh (spent)

Estimated Value Sent : 0.11 LTC (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.

6+ confirmations