← previous blocknext block →recent activity

Analyzing

Block #74,295,354

10 transactions · 7 stateful · 2026-05-13 09:42:26 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,295,354  ·  10 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

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x9a382e4e…98a7

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x59a54ff4…d21b

0x34b655…2a6f

2 touches
0 conflicts

0x5a10b516…7c30

0x34b655…2a6f

2 touches
0 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

2 touches
0 conflicts

0x7117db59…45cd

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x7b7bcac3fe…968fbf

← previous block·next block →recent activity