← previous blocknext block →recent activity

Analyzing

Block #74,508,558

9 transactions · 5 stateful · 2026-05-14 09:21:44 UTC

Parallelism

78/100

Blocked

20%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,508,558  ·  9 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

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x3817764d…242b

0x34b655…2a6f

2 touches
0 conflicts

0x4a6a2a1a…c177

0x34b655…2a6f

2 touches
0 conflicts

0xa433ef1c…2a52

0x34b655…2a6f

2 touches
0 conflicts

0xb8228d38…3953

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 0x9e719c7aca…c7df63

← previous block·next block →recent activity