← previous blocknext block →recent activity

Analyzing

Block #74,786,917

10 transactions · 9 stateful · 2026-05-15 16:25:08 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,786,917  ·  10 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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x801d6be2…acd8

0x065c9d…c394

4 touches
1 conflict

0xe4e1f429…3466

0x065c9d…c394

3 touches
1 conflict

0x725e31c2…cb49

0x065c9d…c394

3 touches
1 conflict

0x2f8bcf56…b638

0x5afd3e…7620

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

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity