← previous blocknext block →recent activity

Analyzing

Block #74,344,396

12 transactions · 9 stateful · 2026-05-13 15:08:37 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,344,396  ·  12 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

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0x91b13e91…855d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfddaacb2…c062

0x34b655…2a6f

4 touches
1 conflict

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x76942a61…d86b

0x1efe02…37d6

2 touches
0 conflicts

0x9c8d6dd6…d619

0xea1b8e…c5ec

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: 0xfd44b351…7f00d1

1 conflict on slot 0x00bac0131a…bba28c

← previous block·next block →recent activity