← previous blocknext block →recent activity

Analyzing

Block #74,410,316

9 transactions · 7 stateful · 2026-05-13 22:27:24 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,410,316  ·  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

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x2d73108e…ca8c

0x065c9d…c394

2 touches
0 conflicts

0x43e05205…bae6

0x065c9d…c394

2 touches
0 conflicts

0x75c5222a…8291

0x065c9d…c394

2 touches
0 conflicts

0x8f2d4996…a83c

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 0xedb848fed2…6e6534

← previous block·next block →recent activity