← previous blocknext block →recent activity

Analyzing

Block #75,079,082

9 transactions · 6 stateful · 2026-05-17 00:56:04 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,079,082  ·  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

0x90687d94…b524

0x34b655…2a6f

4 touches
1 conflict

0xba9f88e8…9c33

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf90ba4b4…6fa0

0x34b655…2a6f

4 touches
1 conflict

0x05b8ccbb…46bc

0x2ab50b…5c41

2 touches
0 conflicts

0x134bb1e3…b524

0x2ab50b…5c41

2 touches
0 conflicts

0x1a52c821…5dd0

0x2ab50b…5c41

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 0x90687d94ce…a3b524

← previous block·next block →recent activity