← previous blocknext block →recent activity

Analyzing

Block #75,335,109

9 transactions · 8 stateful · 2026-05-18 05:27:01 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,335,109  ·  9 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

0x874f5c70…608f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x1294b374…052e

0x065c9d…c394

2 touches
0 conflicts

0x15666037…4366

0x065c9d…c394

2 touches
0 conflicts

0x5f3cd743…9822

0x065c9d…c394

2 touches
0 conflicts

0x88ccea2c…dae7

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: 0x34b6552d…112a6f

1 conflict on slot 0x874f5c70d8…09608f

← previous block·next block →recent activity