LTC Block fdd922c2bf6d8d5ab039dfd74f5b9320c17649663687ed5f38acbdafd50337a0

Current Depth	376,612
Block Size (bytes)	198,214
Block Virtual Size (vbytes)	142,583
Nonce	1357030992
Merkle Root	3b38e0f5d8b48de3d19af38a8b824c4bbdd3a0aa6f2931c91aa1b85197de5a71
Bits (difficulty target)	436,281,063
Version	536870932
IP Relayed By	161.35.48.197:9333
API Call API Docs

dc6ac676e1f1e6a0f4b9131dad63031a17497ad7fd90d2b00546197ef54e96f6

1 Input Consumed

from Block Reward

2 Outputs Created

12.55930913 LTC to
LajyQBeZaBA1NkZDeY8YT5RYYVRkXMvb2T (spent)

0.0 LTC Null Data Transaction

Value Transacted : 12.55930913 LTC

24e88c7e5ba949668ff90a91744574d5a6217fb4739ca514a086e4297cb2d065

1 Input Consumed

3.33056557 LTC from
ltc1qn4wa8gp49rrnl4z02n0j6kqtengvtg3kuarq5e (output)

2 Outputs Created

0.19419699 LTC to
MW1fdUw4zpC89k4T8A6CUuHjfrfAUp9z8y (spent)

3.12358858 LTC to
ltc1qn4wa8gp49rrnl4z02n0j6kqtengvtg3kuarq5e (spent)

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

2103574cf0c89c4bae5cfe7f154e2cd8cf5a12bc880dd663964f68f9b272c1b0

1 Input Consumed

0.64536127 LTC from
ltc1qhz8lx8287yt4grewyqxk39fl4z4j7adx9y5w9l (output)

2 Outputs Created

0.36 LTC to
LYMwLm9v1Y6fywvRrTn6g1UjAHWPU8xUsp (spent)

0.27816127 LTC to
ltc1qhz8lx8287yt4grewyqxk39fl4z4j7adx9y5w9l (spent)

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

f16cd39062777ed8004c8332e53497a63c69ee723c28408f7c7261d18503cb0c

21 Inputs Consumed

0.523162 LTC from
ltc1qhxm6p49sgd2xtxyfg2psgyrg9xhqpckam0tuac (output)

0.523951 LTC from
ltc1qhxm6p49sgd2xtxyfg2psgyrg9xhqpckam0tuac (output)

0.532062 LTC from
ltc1qhxm6p49sgd2xtxyfg2psgyrg9xhqpckam0tuac (output)

0.55199323 LTC from
ltc1qhxm6p49sgd2xtxyfg2psgyrg9xhqpckam0tuac (output)

0.563202 LTC from
ltc1qhxm6p49sgd2xtxyfg2psgyrg9xhqpckam0tuac (output)

...

2 Outputs Created

20.0 LTC to
LW16RQMXY2DfvVVVKaBfmUSiiRii9wkZk2 (spent)

0.21949559 LTC to
ltc1qhxm6p49sgd2xtxyfg2psgyrg9xhqpckam0tuac (spent)

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

e1be89cc3f567a45235efde1dd991cc29c9e45e13408b1456a558ffc7f30f27e

1 Input Consumed

1.91671437 LTC from
MD2ZyR64MfU7true5cTFr2oK49hmR39xMT (output)

2 Outputs Created

0.19593507 LTC to
LeFaPg5aXYeYJVLc6r29DzP2ZnVAok5bYQ (spent)

1.7199793 LTC to
MSKb3g4JsSVyzRMcorKudvUa6q9HZCryM9 (spent)

Value Transacted : 1.91591437 LTC

af66b73577e42edef562cdf611c3e0b6479fa3bf28a27268252c60670ec678a4

1 Input Consumed

2.27090413 LTC from
MJyf3JqTiNMrb5ifTPGWH4spnsqAjGA6tL (output)

2 Outputs Created

0.53442594 LTC to
MFSTqByZaj7Rn1VsLGYNSMpeaVyarYUW3B (spent)

1.73581419 LTC to
MV8x64rtjB2uKzWrjihg77WLUUcdkWuNrH (spent)

Value Transacted : 2.27024013 LTC

61ba0f23d6caa68be6b61b0f2d7031c12929ed2a03bb5d37cf7b3ca92c3e2352

1 Input Consumed

0.61588536 LTC from
MPQK3S1X3Ku2scVXpo9iFEwv2jsViEf86D (output)

2 Outputs Created

0.0614854 LTC to
MPQK3S1X3Ku2scVXpo9iFEwv2jsViEf86D (spent)

0.55377221 LTC to
MJYY1JRu9h8Wtyr1D6Krxx6uhUxaTnn5XG (spent)

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