Block #71,449,858

← previous blocknext block →recent activity

Analyzing

Block #71,449,858

21 transactions · 19 stateful · 2026-04-30 05:29:03 UTC

Parallelism

57/100

Blocked

47%

Avg conflicts / tx

1.62

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,449,858  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0xa4e5d7a6…ca33

0x34b655…2a6f

10 touches
10 conflicts

0xaa3492db…3703

0x34b655…2a6f

10 touches
10 conflicts

0x77905798…fe3d

0x34b655…2a6f

10 touches
10 conflicts

0x451e482b…7e7d

0x34b655…2a6f

10 touches
10 conflicts

0x32ee90db…decc

0x34b655…2a6f

8 touches
6 conflicts

0x5728edaf…f1d4

0x34b655…2a6f

8 touches
6 conflicts

0x578e7f66…1b56

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity