Block #71,042,552

← previous blocknext block →recent activity

Analyzing

Block #71,042,552

22 transactions · 17 stateful · 2026-04-28 08:16:05 UTC

Parallelism

77/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,042,552  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x17fadf32…41c7

0x065c9d…c394

5 touches
3 conflicts

0xa32a11f2…b783

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb6599b96…1024

0x065c9d…c394

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity