← previous blocknext block →recent activity

Analyzing

Block #73,795,831

14 transactions · 11 stateful · 2026-05-11 02:15:08 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,795,831  ·  14 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

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x544ac270…ab6b

0x3bd359…433a

4 touches
1 conflict

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x03a40943…4d6b

0x34b655…2a6f

2 touches
0 conflicts

0x52f0ed22…19f8

0x34b655…2a6f

2 touches
0 conflicts

0x54586137…bae1

0x34b655…2a6f

2 touches
0 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

2 touches
0 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

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: 0x681e908b…e1ae09

3 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity