← previous blocknext block →recent activity

Analyzing

Block #75,735,227

20 transactions · 14 stateful · 2026-05-20 02:05:23 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,735,227  ·  20 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

0x03eaa79f…a9df

0x34b655…2a6f

6 touches
3 conflicts

0xb7b446d2…2006

0x34b655…2a6f

6 touches
3 conflicts

0xb80e2383…946d

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xa3ff1ab2…8ae3

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

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

3 conflicts on slot 0x03eaa79f4b…72a9df

← previous block·next block →recent activity