Block #73,200,644

← previous blocknext block →recent activity

Analyzing

Block #73,200,644

9 transactions · 7 stateful · 2026-05-08 07:59:39 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,200,644  ·  9 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

0x635dca57…ae01

0x34b655…2a6f

4 touches
1 conflict

0x251861eb…78fd

0x34b655…2a6f

4 touches
1 conflict

0x23f97620…fc3b

0xd32edf…ff58

3 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x14dc57ff…37fd

0x34b655…2a6f

2 touches
0 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

2 touches
0 conflicts

0x21d22421…0b7a

0x34b655…2a6f

2 touches
0 conflicts

0x23114fac…630a

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: 0x34b6552d…112a6f

1 conflict on slot 0x635dca5700…c9ae01

← previous block·next block →recent activity