← previous blocknext block →recent activity

Analyzing

Block #74,328,804

9 transactions · 8 stateful · 2026-05-13 13:24:56 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,328,804  ·  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

0xca61a5a4…f49f

0x34b655…2a6f

4 touches
1 conflict

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0xf3477df9…dcdb

0x34b655…2a6f

4 touches
1 conflict

0x161db613…d254

0x34b655…2a6f

4 touches
1 conflict

0x5e1c23e9…4f81

0x34b655…2a6f

4 touches
1 conflict

0x82134a21…d208

0x34b655…2a6f

3 touches
1 conflict

0xa9988419…9f45

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 0xca61a5a41a…aef49f

← previous block·next block →recent activity