← previous blocknext block →recent activity

Analyzing

Block #74,505,220

14 transactions · 9 stateful · 2026-05-14 08:59:16 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,505,220  ·  14 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa798af71…f2ab

0x065c9d…c394

4 touches
1 conflict

0x28cc3374…7409

0x065c9d…c394

4 touches
1 conflict

0xc47a816d…3d86

0x065c9d…c394

3 touches
1 conflict

0x61a465f8…4a48

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xa7f89e3d…b7ff

0x065c9d…c394

2 touches
0 conflicts

0xafd18c42…05e1

0x065c9d…c394

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity