← previous blocknext block →recent activity

Analyzing

Block #71,177,838

24 transactions · 22 stateful · 2026-04-28 23:17:10 UTC

Parallelism

79/100

Blocked

45%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,177,838  ·  24 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

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0x148e0217…34a2

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 conflicts

0x5a9c2dc3…43ab

0x34b655…2a6f

6 touches
3 conflicts

0x5f251b96…6054

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

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 0x8c49c85c3e…afee96

← previous block·next block →recent activity