Block #73,960,387

← previous blocknext block →recent activity

Analyzing

Block #73,960,387

11 transactions · 9 stateful · 2026-05-11 20:31:34 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,960,387  ·  11 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

0x41629728…ee69

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

3 touches
1 conflict

0xcbecfb96…3e12

0x7b2728…7777

3 touches
1 conflict

0x17cd1479…00bb

0x8d66a4…3095

3 touches
1 conflict

0x2ed00f98…da9f

0x34b655…2a6f

2 touches
0 conflicts

0x336241b2…c1db

0x34b655…2a6f

2 touches
0 conflicts

0x367ecc15…6a74

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 0x41629728ed…c3ee69

← previous block·next block →recent activity