← previous blocknext block →recent activity

Analyzing

Block #73,705,559

14 transactions · 10 stateful · 2026-05-10 16:05:57 UTC

Parallelism

71/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,705,559  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xaa8a1c54…ead3

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x1f920221…df46

0x34b655…2a6f

2 touches
0 conflicts

0x23951077…539b

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x263996f9…ba87

0x34b655…2a6f

2 touches
0 conflicts

0x28933977…81c5

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 0xaa8a1c5424…edead3

← previous block·next block →recent activity