← previous blocknext block →recent activity

Analyzing

Block #75,622,164

25 transactions · 21 stateful · 2026-05-19 13:32:04 UTC

Parallelism

80/100

Blocked

48%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,622,164  ·  25 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x54e710f5…37ff

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x67faf0c9…2ddb

0x34b655…2a6f

4 touches
1 conflict

0x6b732abc…fc85

0x34b655…2a6f

4 touches
1 conflict

0x726c7f8e…1974

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity