← previous blocknext block →recent activity

Analyzing

Block #73,609,427

11 transactions · 8 stateful · 2026-05-10 05:18:40 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,609,427  ·  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

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x749437cf…2fc0

0x2880ab…7b43

2 touches
0 conflicts

0x749437cf…2fc1

0x2880ab…7b43

2 touches
0 conflicts

0x4060605b…75a3

0x3bd359…433a

2 touches
0 conflicts

0x57a37dda…8712

0x3bd359…433a

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 0x9ea57326ca…60329f

← previous block·next block →recent activity