← previous blocknext block →recent activity

Analyzing

Block #73,016,017

28 transactions · 25 stateful · 2026-05-07 11:31:06 UTC

Parallelism

71/100

Blocked

48%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,016,017  ·  28 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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0xc4e9d729…dacb

0xd32edf…ff58

7 touches
6 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0x0f96132c…1715

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

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: 0x065c9d28…a9c394

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity