← previous blocknext block →recent activity

Analyzing

Block #75,095,959

10 transactions · 9 stateful · 2026-05-17 02:48:44 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,095,959  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4aacac7e…d614

0x065c9d…c394

3 touches
1 conflict

0x04f5c2b7…3747

0x065c9d…c394

3 touches
1 conflict

0x132f064d…c518

0x065c9d…c394

2 touches
0 conflicts

0x2fe1aef1…877f

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x8c482595…168f

0x065c9d…c394

2 touches
0 conflicts

0xf3c1af59…0691

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 0x0000000000…00003d

← previous block·next block →recent activity