← previous blocknext block →recent activity

Analyzing

Block #72,979,716

27 transactions · 20 stateful · 2026-05-07 07:29:30 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1.37

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,979,716  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

8 touches
6 conflicts

0x3e4b8d9f…b8a7

0x6ca43f…c331

8 touches
6 conflicts

0x1a4b4152…0a08

0x6ca43f…c331

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0xc81a3270…ad19

0xd32edf…ff58

7 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

28 conflicts on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity