Block #71,451,074

← previous blocknext block →recent activity

Analyzing

Block #71,451,074

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

Parallelism

48/100

Blocked

60%

Avg conflicts / tx

2.52

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,451,074  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x1c913164…5c2e

0x34b655…2a6f

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

12 touches
15 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

12 touches
15 conflicts

0x32ee90db…decc

0x34b655…2a6f

12 touches
15 conflicts

0x5728edaf…f1d4

0x34b655…2a6f

12 touches
15 conflicts

0x578e7f66…1b56

0x34b655…2a6f

12 touches
15 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

12 touches
15 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

36 conflicts on slot 0x1c913164f5…845c2e

← previous block·next block →recent activity