Block #73,359,570

← previous blocknext block →recent activity

Analyzing

Block #73,359,570

17 transactions · 16 stateful · 2026-05-09 01:36:49 UTC

Parallelism

65/100

Blocked

63%

Avg conflicts / tx

1.24

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,359,570  ·  17 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

10 touches
10 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0x1acaa26f…7b77

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x8f5f4694…b6f3

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x23951077…539b

0x34b655…2a6f

6 touches
3 conflicts

0x64e30b79…bc29

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity