Dogecoin Block 3,569,590

74ec9550c95182783568f2f0886bd1394a1cae785643e35f9f8d0e5a9b132774

  • Received
  • Total Transacted
    3,170,792.9425 DOGE
  • Total Fees
    10.152 DOGE

Current Depth 1,619,317
Block Size (bytes) 4,235
Nonce 0
Merkle Root 373dfca2c215df77cbe9146707921a1b1866b7d6fca187d385b7704902b0a496
Bits (difficulty target) 436,426,639
Version 6422788
API Call API Docs

5 Transactions

Page 1 of 1

91ae3465edd7a6f7b6650ced6bc8ea9541c854bde4a3893dc130ea34d53cd331

1 Input Consumed

from Block Reward

1 Output Created

Value Transacted : 10,010.152 DOGE

b069d17e2faa709b212a0bcf66e1268a041f4049d92afa1135ec6cdb293926b6

1 Input Consumed

2,988,004.29896 DOGE from
DAdwtsBsNDuBoEp2nsLVbN4dsSkpS6fEkF (output)

2 Outputs Created

2,986,954.88576 DOGE to
DLzCvKskasu4Adj3XgbyNitKBukBSa5JPP (spent)

Value Transacted : 2,988,002.14696 DOGE

37b151cd4813c7e2c8f258ca0049337766b54a67985a868cf8ac7c0d0d64baca

8 Inputs Consumed

226.55376738 DOGE from
DGKEzfhn3gpH2Ku8E8AfsN57gRnwbU6vZ6 (output)
69.65356178 DOGE from
DMqqakTjLGNi6V2X3cFsgGnTTJCKeqiQeV (output)
...

5 Outputs Created

17,187.29274349 DOGE to
DFu5bncaUtTcBF89LDcjmAiNAZVyV3hKd4 (spent)
1,920.02799999 DOGE to
DQQHPu95rHpyRqHcmhYMz4XfBrsYfF39dL (spent)
100,010.9113 DOGE to
DEy11h3wuphJo7HseQyUDC8B3oSRZD8Bo8 (spent)

Value Transacted : 129,118.25412789 DOGE

02287d878cd5830fb34984b7aabba86753cfaa1c4174ccca9781a3920c420592

14 Inputs Consumed

7,884.53467883 DOGE from
DR4qYNZc5e9Ah3ADvXUNTiN13m3HV8d6bm (output)
3,438.54904 DOGE from
DQp84cHajPHBhPh5vP1rkXntJW5ADPfBgy (output)
1,553.57712404 DOGE from
DSJAEiZeX6ep3cfg582FXYPEKsqmCVrwtU (output)
...

2 Outputs Created

Value Transacted : 28,531.01049434 DOGE

dbc7fd6c02fd043b3582eba0fe8af7c0e6c9e3bff4637d88d3ec641d57d80e05

1 Input Consumed

25,142.53090904 DOGE from
9vqmNNhqJaVntZ2JzFkMiH9Fk93wPymix7 (output)

2 Outputs Created

24,937.53090904 DOGE to
9vqmNNhqJaVntZ2JzFkMiH9Fk93wPymix7 (spent)

Estimated Value Sent : 204.0 DOGE ()

"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.
Page 1 of 1