Block #71,042,258

← previous blocknext block →recent activity

Analyzing

Block #71,042,258

22 transactions · 20 stateful · 2026-04-28 08:14:09 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,042,258  ·  22 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x005fb969…2d97

0x34b655…2a6f

6 touches
3 conflicts

0x0520da1d…c88e

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x40967308…1b6d

0x34b655…2a6f

6 touches
3 conflicts

0x65e795ca…0320

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity