Block #73,034,068

← previous blocknext block →recent activity

Analyzing

Block #73,034,068

13 transactions · 13 stateful · 2026-05-07 13:31:17 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,034,068  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x5471800f…b5da

0x065c9d…c394

6 touches
3 conflicts

0x603ff5b7…fc32

0x065c9d…c394

6 touches
3 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

6 touches
3 conflicts

0x0a2250a8…3cb1

0x34b655…2a6f

6 touches
3 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity