← previous blocknext block →recent activity

Analyzing

Block #74,338,199

9 transactions · 8 stateful · 2026-05-13 14:27:26 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,338,199  ·  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

0xb9a98983…c38f

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x28bce6ed…1d79

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x9a69fe57…7e9f

0x0555e3…2b9c

2 touches
0 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

2 touches
0 conflicts

0xffe431af…8faa

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 0xb9a989839f…c8c38f

← previous block·next block →recent activity