← previous blocknext block →recent activity

Analyzing

Block #74,344,453

10 transactions · 9 stateful · 2026-05-13 15:09:00 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,344,453  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x3623900f…1c70

0x34b655…2a6f

2 touches
0 conflicts

0x499adbcf…eb20

0x34b655…2a6f

2 touches
0 conflicts

0x5675c293…17d9

0x34b655…2a6f

2 touches
0 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

2 touches
0 conflicts

0x85868b0e…a446

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity