← previous blocknext block →recent activity

Analyzing

Block #71,289,723

27 transactions · 24 stateful · 2026-04-29 11:41:34 UTC

Parallelism

78/100

Blocked

58%

Avg conflicts / tx

1.19

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,289,723  ·  27 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

0xa06b3a88…c732

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0xd5b10148…e635

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

8 touches
6 conflicts

0x150af51d…9c42

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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: 0xd32edf66…9fff58

15 conflicts on slot 0xa06b3a881c…33c732

← previous block·next block →recent activity