← previous blocknext block →recent activity

Analyzing

Block #74,505,157

17 transactions · 11 stateful · 2026-05-14 08:58:50 UTC

Parallelism

76/100

Blocked

27%

Avg conflicts / tx

0.18

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,505,157  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x45b9e08c…a11b

0x34b655…2a6f

2 touches
0 conflicts

0x55888ede…6745

0x34b655…2a6f

2 touches
0 conflicts

0x622df421…3ad6

0x34b655…2a6f

2 touches
0 conflicts

0x6d3780e3…0829

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 0xf853eb8e72…d84027

← previous block·next block →recent activity