← previous blocknext block →recent activity

Analyzing

Block #72,287,961

34 transactions · 27 stateful · 2026-05-04 02:40:21 UTC

Parallelism

85/100

Blocked

67%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,287,961  ·  34 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

0x0cd1564b…a23b

0xd32edf…ff58

9 touches
10 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xdf671536…aa02

0x34b655…2a6f

6 touches
3 conflicts

0xfadc118d…5d64

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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

10 conflicts on slot 0x0cd1564b8f…7ea23b

← previous block·next block →recent activity