← previous blocknext block →recent activity

Analyzing

Block #73,176,230

19 transactions · 19 stateful · 2026-05-08 05:17:00 UTC

Parallelism

74/100

Blocked

32%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,176,230  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2a354a63…0515

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0xbe629991…c816

0x065c9d…c394

6 touches
3 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

6 touches
3 conflicts

0xce2832cc…6f9d

0x065c9d…c394

5 touches
3 conflicts

0xf0f673fd…37a7

0x6ca43f…c331

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

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 0x2a354a6333…480515

← previous block·next block →recent activity