← previous blocknext block →recent activity

Analyzing

Block #75,103,266

8 transactions · 7 stateful · 2026-05-17 03:37:30 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,103,266  ·  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

0x37f59ead…14dd

0x065c9d…c394

4 touches
1 conflict

0x58c1a83e…ef16

0x065c9d…c394

3 touches
1 conflict

0x2813b0bd…ffaf

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x090c940f…91cb

0x065c9d…c394

2 touches
0 conflicts

0x436c57e0…51c3

0x065c9d…c394

2 touches
0 conflicts

0x87eb8b4a…e84f

0x065c9d…c394

2 touches
0 conflicts

0xb32ccdc1…d408

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 0x37f59ead3e…6a14dd

← previous block·next block →recent activity