Block #73,500,094

← previous blocknext block →recent activity

Analyzing

Block #73,500,094

14 transactions · 11 stateful · 2026-05-09 17:12:00 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,500,094  ·  14 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

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xc927e871…363c

0x065c9d…c394

4 touches
1 conflict

0x21a14a06…3901

0x065c9d…c394

3 touches
1 conflict

0x02e3db33…6d97

0x065c9d…c394

3 touches
1 conflict

0xf7967f5f…fc2a

0x065c9d…c394

3 touches
1 conflict

0x7da2a76f…0e2b

0x065c9d…c394

2 touches
0 conflicts

0x7ffb7084…d97b

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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity