Block #71,092,541

← previous blocknext block →recent activity

Analyzing

Block #71,092,541

30 transactions · 25 stateful · 2026-04-28 13:49:07 UTC

Parallelism

80/100

Blocked

52%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,092,541  ·  30 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

0x3f2072c7…ca04

0xd32edf…ff58

9 touches
10 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x1e9fccc4…5c21

0x34b655…2a6f

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

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

10 conflicts on slot 0x3f2072c75d…afca04

← previous block·next block →recent activity