← previous blocknext block →recent activity

Analyzing

Block #74,239,352

14 transactions · 9 stateful · 2026-05-13 03:30:04 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,239,352  ·  14 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

0x45cc35d8…391b

0xd32edf…ff58

5 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xca0fef1c…b548

0x34b655…2a6f

3 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

3 touches
1 conflict

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: 0xd32edf66…9fff58

3 conflicts on slot 0x45cc35d867…6b391b

← previous block·next block →recent activity