Block #71,683,602

← previous blocknext block →recent activity

Analyzing

Block #71,683,602

24 transactions · 17 stateful · 2026-05-01 07:29:11 UTC

Parallelism

58/100

Blocked

65%

Avg conflicts / tx

1.75

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,683,602  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x5d3f901b…91f3

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

8 touches
6 conflicts

0x08f79637…a047

0x065c9d…c394

7 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

36 conflicts on slot 0x5d3f901bb7…2c91f3

← previous block·next block →recent activity