← previous blocknext block →recent activity

Analyzing

Block #75,128,388

9 transactions · 7 stateful · 2026-05-17 06:25:13 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,128,388  ·  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

0x537e2e5b…c3ab

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0xab981df1…2941

0x34b655…2a6f

4 touches
1 conflict

0xfbde3c84…c97c

0x34b655…2a6f

4 touches
1 conflict

0x29cd05f5…390c

0x34b655…2a6f

4 touches
1 conflict

0x01737532…9b12

0x34b655…2a6f

4 touches
1 conflict

0xb3aa2022…9e09

0x34b655…2a6f

3 touches
1 conflict

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

3 conflicts on slot 0x537e2e5b8c…c7c3ab

← previous block·next block →recent activity