← previous blocknext block →recent activity

Analyzing

Block #71,065,032

36 transactions · 30 stateful · 2026-04-28 10:45:45 UTC

Parallelism

86/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,065,032  ·  36 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

0xa02838a3…bc54

0x34b655…2a6f

10 touches
10 conflicts

0x47b807a2…3307

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x3552a26a…ce1f

0x34b655…2a6f

6 touches
3 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

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

10 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity