← previous blocknext block →recent activity

Analyzing

Block #74,361,151

19 transactions · 18 stateful · 2026-05-13 17:00:02 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,361,151  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0x55888ede…6745

0x34b655…2a6f

6 touches
3 conflicts

0x4582e32d…1abe

0x34b655…2a6f

4 touches
1 conflict

0x5a9c2dc3…43ab

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity