← previous blocknext block →recent activity

Analyzing

Block #75,541,932

11 transactions · 11 stateful · 2026-05-19 04:36:30 UTC

Parallelism

55/100

Blocked

36%

Avg conflicts / tx

0.91

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,541,932  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfd784183…67bb

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x76ffd680…db23

0x34b655…2a6f

4 touches
1 conflict

0xcab72563…329a

0x34b655…2a6f

4 touches
1 conflict

0xd6d040d9…9ae3

0x34b655…2a6f

4 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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity