Block #72,976,073

← previous blocknext block →recent activity

Analyzing

Block #72,976,073

29 transactions · 24 stateful · 2026-05-07 07:05:16 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,976,073  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xdaca243a…f9de

0x34b655…2a6f

8 touches
6 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd68117c2…da2c

0xd32edf…ff58

7 touches
6 conflicts

0x150af51d…9c42

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x8aa1941d…2988

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 0xdaca243a5e…09f9de

← previous block·next block →recent activity