Block #71,741,568

← previous blocknext block →recent activity

Analyzing

Block #71,741,568

26 transactions · 21 stateful · 2026-05-01 13:55:11 UTC

Parallelism

77/100

Blocked

48%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,741,568  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe6c2a56d…4780

0x065c9d…c394

9 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x93b13bc1…d1ce

0xd32edf…ff58

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xe17acb5e…7063

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

10 conflicts on slot 0xe6c2a56d00…114780

← previous block·next block →recent activity