← previous blocknext block →recent activity

Analyzing

Block #73,682,609

18 transactions · 16 stateful · 2026-05-10 13:31:16 UTC

Parallelism

83/100

Blocked

25%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb08dfc05…4923

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xa698cdcb…5aef

0x34b655…2a6f

4 touches
1 conflict

0x06c0af84…8d00

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

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 0xb91a6f59b9…c8722c

← previous block·next block →recent activity