← previous blocknext block →recent activity

Analyzing

Block #74,331,225

13 transactions · 9 stateful · 2026-05-13 13:41:03 UTC

Parallelism

85/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,331,225  ·  13 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

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x4a6a2a1a…c177

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x11560115…bfc2

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0x5860c4f3…0c39

0x3bd359…433a

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 0x3347cbe5ae…92846c

← previous block·next block →recent activity