← previous blocknext block →recent activity

Analyzing

Block #73,201,929

38 transactions · 24 stateful · 2026-05-08 08:08:13 UTC

Parallelism

89/100

Blocked

46%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,201,929  ·  38 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

0x3b8ffd61…f3ad

0x34b655…2a6f

8 touches
6 conflicts

0x615ab167…135c

0xd32edf…ff58

7 touches
6 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x4582e32d…1abe

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0x3b8ffd6160…92f3ad

← previous block·next block →recent activity