← previous blocknext block →recent activity

Analyzing

Block #75,262,605

13 transactions · 11 stateful · 2026-05-17 21:21:40 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,262,605  ·  13 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0x6d8c1aac…1f95

0x065c9d…c394

3 touches
1 conflict

0x4570f6e1…c787

0x065c9d…c394

3 touches
1 conflict

0xf809f1b6…f138

0x065c9d…c394

2 touches
0 conflicts

0x03622417…0bd6

0x2880ab…7b43

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity