Block #71,451,065

← previous blocknext block →recent activity

Analyzing

Block #71,451,065

20 transactions · 20 stateful · 2026-04-30 05:37:06 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,451,065  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x1c913164…5c2e

0x34b655…2a6f

12 touches
15 conflicts

0xc83595c6…fece

0x34b655…2a6f

10 touches
10 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

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

0xc6417de0…2191

0xc8689a…ee79

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