← previous blocknext block →recent activity

Analyzing

Block #73,686,795

31 transactions · 25 stateful · 2026-05-10 13:59:27 UTC

Parallelism

84/100

Blocked

48%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,686,795  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf1c6ad50…5424

0xd32edf…ff58

9 touches
10 conflicts

0x3e733ae4…4598

0x34b655…2a6f

8 touches
6 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x148f33fb…5af3

0x34b655…2a6f

4 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

4 touches
1 conflict

0x1f876d5b…dee3

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

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: 0xd32edf66…9fff58

10 conflicts on slot 0xf1c6ad50b6…f05424

← previous block·next block →recent activity