Block #72,209,422

← previous blocknext block →recent activity

Analyzing

Block #72,209,422

37 transactions · 31 stateful · 2026-05-03 17:52:31 UTC

Parallelism

86/100

Blocked

48%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,209,422  ·  37 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x09c8fce2…768f

0xd32edf…ff58

7 touches
6 conflicts

0x3c7852ab…feea

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x4ac5588f…e61f

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: 0x3bd359c1…15433a

6 conflicts on slot 0xce8bbe3367…8cb72e

← previous block·next block →recent activity