Block #73,338,413

← previous blocknext block →recent activity

Analyzing

Block #73,338,413

12 transactions · 11 stateful · 2026-05-08 23:16:08 UTC

Parallelism

50/100

Blocked

45%

Avg conflicts / tx

1.25

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,338,413  ·  12 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

0x0b390c61…dc07

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x57ccbfc9…4b08

0x065c9d…c394

2 touches
0 conflicts

0xa0033c11…6ba7

0x065c9d…c394

2 touches
0 conflicts

0xa46741a1…954c

0x065c9d…c394

2 touches
0 conflicts

0xf35f9ea6…d0ac

0x065c9d…c394

2 touches
0 conflicts

0xff23f340…55f1

0x065c9d…c394

2 touches
0 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