LTC Address LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1

6+ confirmations

b3a4d2b33b4551ee8e469f8f2684eeb7ccd1f1a1ca9344bc0e56f23f0a3972bf

1 Input Consumed

10.0 LTC from
LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1 (output)

2 Outputs Created

7.0 LTC to
LMRFxzEN4oYqhVrEtKN2UQnD4hj1pYcK9f (spent)

2.999322 LTC to
LXBNbn69tKDaXLzvWncLQf1Wa1go8J14eb (spent)

Value Transacted : 9.999322 LTC

6+ confirmations

5f00f1c7fe5322ae85007aa1c030b4745581efe6d99b5ab53dde0aae9cf67759

1 Input Consumed

20.0 LTC from
LMRFxzEN4oYqhVrEtKN2UQnD4hj1pYcK9f (output)

2 Outputs Created

9.999322 LTC to
LMRFxzEN4oYqhVrEtKN2UQnD4hj1pYcK9f (spent)

10.0 LTC to
LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1 (spent)

Estimated Value Sent : 10.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

9f8b644e7ca1fb9ebe705534fda25fd0fcda8cb3bf77baecbc123c3103a60fb2

1 Input Consumed

6.92838527 LTC from
LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1 (output)

2 Outputs Created

0.2 LTC to
M9QsyDVSy4AdTwpr9cogECS7wB4mu5uSZ9 (spent)

6.72771327 LTC to
LhJS5BoDMymciepN6D6uzTnQJgaJ1eHyyR (spent)

Value Transacted : 6.92771327 LTC

6+ confirmations

ce52a4ee23e23485e2598ffa98bc14c39aff265442ec52806a01bfb0fb5f1359

2 Inputs Consumed

0.48545699 LTC from
LMYKBrogF9JVTgxTjK9z8kvzBnPp6gN14G (output)

6.92838527 LTC from
LMYKBrogF9JVTgxTjK9z8kvzBnPp6gN14G (output)

2 Outputs Created

6.92838527 LTC to
LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1 (spent)

0.48545325 LTC to
LMYKBrogF9JVTgxTjK9z8kvzBnPp6gN14G (spent)

Estimated Value Sent : 6.92838527 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

d5db5a8b48bd37d0639394988cfff0ee204a6a21dd0ca6610789b0580deded04

1 Input Consumed

6.90308958 LTC from
LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1 (output)

1 Output Created

6.90241158 LTC to
MKNHtQf5b13H4kaTpHGpfnGRPD4akDRkjE (spent)

Value Transacted : 6.90241158 LTC

6+ confirmations

977e6ba68f82b71879ed079cb37916f80a3397dbcd995fbf769e7ef89de119c3

1 Input Consumed

7.12953082 LTC from
LMYKBrogF9JVTgxTjK9z8kvzBnPp6gN14G (output)

2 Outputs Created

6.90308958 LTC to
LXJ6hGAADtA4jLQiEDpJnJ2v1s7ceEJrN1 (spent)

0.22643898 LTC to
LMYKBrogF9JVTgxTjK9z8kvzBnPp6gN14G (spent)

Estimated Value Sent : 6.90308958 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