← previous blocknext block →recent activity

Analyzing

Block #73,651,802

11 transactions · 9 stateful · 2026-05-10 10:03:16 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,651,802  ·  11 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

0x692ebaf8…b3ca

0xd32edf…ff58

5 touches
3 conflicts

0x69bed3c2…6fd6

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xda68c75f…2912

0x34b655…2a6f

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xa70f472b…ea64

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

3 conflicts on slot 0x692ebaf873…4bb3ca

← previous block·next block →recent activity