← previous blocknext block →recent activity

Analyzing

Block #71,036,851

21 transactions · 15 stateful · 2026-04-28 07:38:09 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,036,851  ·  21 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

8 touches
6 conflicts

0x0520da1d…c88e

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x65e795ca…0320

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

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 0xa02838a385…ffbc54

← previous block·next block →recent activity