← previous blocknext block →recent activity

Analyzing

Block #74,508,521

10 transactions · 7 stateful · 2026-05-14 09:21:29 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,508,521  ·  10 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

0xcb63cb0a…66a9

0x34b655…2a6f

4 touches
1 conflict

0x4a6a2a1a…c177

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x041ee703…b4c1

0x34b655…2a6f

2 touches
0 conflicts

0x2d5e3771…9a87

0x34b655…2a6f

2 touches
0 conflicts

0x4582e32d…1abe

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

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 0xcb63cb0ac3…9a66a9

← previous block·next block →recent activity