← previous blocknext block →recent activity

Analyzing

Block #73,809,592

11 transactions · 8 stateful · 2026-05-11 03:47:30 UTC

Parallelism

73/100

Blocked

25%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,809,592  ·  11 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

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0x2d975111…5f52

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x37cfaf01…4a46

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

2 touches
0 conflicts

0x8c315b05…51c7

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

3 conflicts on slot 0x6eba5e7f6a…ac4b52

← previous block·next block →recent activity