← previous blocknext block →recent activity

Analyzing

Block #74,525,269

9 transactions · 8 stateful · 2026-05-14 11:14:21 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,525,269  ·  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

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0xe57fd50c…ed92

0x34b655…2a6f

4 touches
1 conflict

0xfe37be0f…4fa0

0x065c9d…c394

4 touches
1 conflict

0x719f4ab6…aae7

0x065c9d…c394

3 touches
1 conflict

0x080674a3…e550

0x065c9d…c394

3 touches
1 conflict

0x916b2130…a74e

0x065c9d…c394

2 touches
0 conflicts

0x9cf78dbd…5398

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: 0x065c9d28…a9c394

1 conflict on slot 0x47b807a243…c53307

← previous block·next block →recent activity