Block #71,065,633

← previous blocknext block →recent activity

Analyzing

Block #71,065,633

23 transactions · 16 stateful · 2026-04-28 10:49:45 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,065,633  ·  23 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

0xa02838a3…bc54

0x34b655…2a6f

12 touches
15 conflicts

0x005fb969…2d97

0x34b655…2a6f

6 touches
3 conflicts

0x06c8fd5b…110f

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0x40967308…1b6d

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

15 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity