← previous blocknext block →recent activity

Analyzing

Block #74,335,752

22 transactions · 16 stateful · 2026-05-13 14:11:07 UTC

Parallelism

91/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,335,752  ·  22 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

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xa90e52fe…7eb1

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0x99f080dc…58c1

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

2 touches
0 conflicts

0x9be2b99a…a959

0x34b655…2a6f

2 touches
0 conflicts

0xf853eb8e…4027

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 0x62d080e928…5a4a7c

← previous block·next block →recent activity