Block #73,383,555

← previous blocknext block →recent activity

Analyzing

Block #73,383,555

10 transactions · 8 stateful · 2026-05-09 04:16:24 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,383,555  ·  10 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

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x078118d8…7b19

0x065c9d…c394

2 touches
0 conflicts

0x51cb13fc…f1a5

0x065c9d…c394

2 touches
0 conflicts

0x60e860fa…46e4

0x065c9d…c394

2 touches
0 conflicts

0x7f0982ad…5faa

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity