← previous blocknext block →recent activity

Analyzing

Block #74,298,693

9 transactions · 8 stateful · 2026-05-13 10:04:42 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,298,693  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xeb673994…b86e

0x065c9d…c394

4 touches
1 conflict

0x61983445…d52e

0x065c9d…c394

4 touches
1 conflict

0xb7df0d1d…903c

0x065c9d…c394

3 touches
1 conflict

0x919f6975…434f

0x065c9d…c394

3 touches
1 conflict

0x10c8621d…6ce0

0x065c9d…c394

2 touches
0 conflicts

0x12535e11…b23c

0x065c9d…c394

2 touches
0 conflicts

0xb0952f70…5896

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

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

1 conflict on slot 0xeb67399457…fab86e

← previous block·next block →recent activity