← previous blocknext block →recent activity

Analyzing

Block #73,650,585

11 transactions · 8 stateful · 2026-05-10 09:55:07 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,650,585  ·  11 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x89cfb76a…59e8

0x065c9d…c394

3 touches
1 conflict

0x28d69df7…ec80

0x065c9d…c394

3 touches
1 conflict

0x2a2058d3…b24a

0x065c9d…c394

2 touches
0 conflicts

0x5a7e11bf…c759

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0x93bbfd7b…abd8

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity