← previous blocknext block →recent activity

Analyzing

Block #73,016,053

23 transactions · 20 stateful · 2026-05-07 11:31:20 UTC

Parallelism

52/100

Blocked

75%

Avg conflicts / tx

1.78

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,016,053  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x0b390c61…dc07

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

10 touches
10 conflicts

0x2182d208…6795

0xd32edf…ff58

7 touches
6 conflicts

0xba5743c7…21c6

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf095baf5…1b2b

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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

15 conflicts on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity