Block #72,976,057

← previous blocknext block →recent activity

Analyzing

Block #72,976,057

43 transactions · 27 stateful · 2026-05-07 07:05:09 UTC

Parallelism

81/100

Blocked

56%

Avg conflicts / tx

0.72

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,976,057  ·  43 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x42608568…eb18

0xd32edf…ff58

9 touches
10 conflicts

0x0eac6378…36f4

0x34b655…2a6f

8 touches
6 conflicts

0x150af51d…9c42

0x34b655…2a6f

8 touches
6 conflicts

0x3c35979a…975d

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 conflicts

0x55968d29…1d6a

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0xdaca243a5e…09f9de

← previous block·next block →recent activity