← previous blocknext block →recent activity

Analyzing

Block #72,984,182

27 transactions · 24 stateful · 2026-05-07 07:59:30 UTC

Parallelism

78/100

Blocked

54%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,984,182  ·  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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x468f66ff…e6f3

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity