← previous blocknext block →recent activity

Analyzing

Block #74,328,691

21 transactions · 13 stateful · 2026-05-13 13:24:11 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.14

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,328,691  ·  21 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

0xae241e60…d96d

0x34b655…2a6f

4 touches
1 conflict

0xe6bc2705…d15b

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x18edc600…f50f

0x34b655…2a6f

4 touches
1 conflict

0x1c0616a8…8ba8

0x34b655…2a6f

2 touches
0 conflicts

0x25de453d…9573

0x34b655…2a6f

2 touches
0 conflicts

0x2c653f98…6e5a

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 0xae241e6050…dcd96d

← previous block·next block →recent activity