← previous blocknext block →recent activity

Analyzing

Block #72,817,365

36 transactions · 24 stateful · 2026-05-06 13:28:24 UTC

Parallelism

83/100

Blocked

54%

Avg conflicts / tx

0.92

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,817,365  ·  36 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

0xbd7e37a9…9eb5

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

10 touches
10 conflicts

0x5c0e6986…fb36

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

8 touches
6 conflicts

0x93afca4c…b47b

0x1b6862…e19c

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

15 conflicts on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity