← previous blocknext block →recent activity

Analyzing

Block #75,127,207

8 transactions · 7 stateful · 2026-05-17 06:17:20 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,127,207  ·  8 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

0xc0be0d6e…7c9f

0x065c9d…c394

4 touches
1 conflict

0xaf52208b…cb7a

0x065c9d…c394

3 touches
1 conflict

0x307e31a9…f77f

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x06ac26e1…60c0

0x065c9d…c394

2 touches
0 conflicts

0x5ab7ccdd…11f1

0x065c9d…c394

2 touches
0 conflicts

0x6ff77f56…dbcc

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xc0be0d6ef8…3e7c9f

← previous block·next block →recent activity