← previous blocknext block →recent activity

Analyzing

Block #74,635,404

9 transactions · 7 stateful · 2026-05-14 23:33:22 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,635,404  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x79fb22b1…dac8

0x065c9d…c394

5 touches
3 conflicts

0x9e5f15ce…810d

0x065c9d…c394

5 touches
3 conflicts

0x29fea63f…f106

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x394240b7…cf18

0x065c9d…c394

2 touches
0 conflicts

0xc36ed1ad…ab46

0x065c9d…c394

2 touches
0 conflicts

0xca04c7ad…7612

0x065c9d…c394

2 touches
0 conflicts

0xe5a0591d…459d

0x065c9d…c394

2 touches
0 conflicts

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 0x79fb22b1f1…56dac8

← previous block·next block →recent activity