← previous blocknext block →recent activity

Analyzing

Block #75,124,643

11 transactions · 9 stateful · 2026-05-17 06:00:12 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,124,643  ·  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

0x8538a5f8…7f37

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5ab7ccdd…11f1

0x065c9d…c394

3 touches
1 conflict

0xf0da41dc…f652

0x065c9d…c394

3 touches
1 conflict

0x1fea0722…698c

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x9d111572…58aa

0x065c9d…c394

2 touches
0 conflicts

0xb7feed21…cdd6

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 0x8538a5f804…c67f37

← previous block·next block →recent activity