← previous blocknext block →recent activity

Analyzing

Block #74,285,683

11 transactions · 9 stateful · 2026-05-13 08:38:02 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,285,683  ·  11 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

0xfd0c57d2…7786

0x065c9d…c394

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xdc86c094…79a5

0x34b655…2a6f

4 touches
1 conflict

0xdc90bed5…58a9

0x34b655…2a6f

4 touches
1 conflict

0xeb09ee55…11b5

0x065c9d…c394

3 touches
1 conflict

0xa2b85a1f…eaed

0x065c9d…c394

3 touches
1 conflict

0x7e810243…d3fb

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

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 0xfd0c57d239…ec7786

← previous block·next block →recent activity