← previous blocknext block →recent activity

Analyzing

Block #73,308,287

13 transactions · 10 stateful · 2026-05-08 19:55:42 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,308,287  ·  13 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

0x6fa48833…eb0d

0x34b655…2a6f

4 touches
1 conflict

0x96c53732…5aac

0x34b655…2a6f

4 touches
1 conflict

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0x189156a9…f03c

0x0ac7c3…d447

2 touches
0 conflicts

0x18e88129…5a60

0x0ac7c3…d447

2 touches
0 conflicts

0x24ef2c46…b42c

0x0ac7c3…d447

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 0x6fa48833f3…adeb0d

← previous block·next block →recent activity