← previous blocknext block →recent activity

Analyzing

Block #75,262,303

9 transactions · 6 stateful · 2026-05-17 21:19:39 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,262,303  ·  9 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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x18b11fba…c92a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x55192654…91fe

0x34b655…2a6f

4 touches
1 conflict

0x0a809ce1…7894

0x34b655…2a6f

2 touches
0 conflicts

0x1ae9195f…9cb7

0x34b655…2a6f

2 touches
0 conflicts

0x206f4379…e08a

0x34b655…2a6f

2 touches
0 conflicts

0x2905340c…dbc6

0x34b655…2a6f

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 0xc824469a90…af6425

← previous block·next block →recent activity