Block #73,200,723

← previous blocknext block →recent activity

Analyzing

Block #73,200,723

13 transactions · 10 stateful · 2026-05-08 08:00:11 UTC

Parallelism

69/100

Blocked

30%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,200,723  ·  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

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x2da196af…5f4e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x687effeb…de1b

0x065c9d…c394

3 touches
1 conflict

0x782c8da4…77b0

0x065c9d…c394

3 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

2 touches
0 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

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

3 conflicts on slot 0x2a354a6333…480515

← previous block·next block →recent activity