Block #73,391,343

← previous blocknext block →recent activity

Analyzing

Block #73,391,343

11 transactions · 11 stateful · 2026-05-09 05:08:14 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,391,343  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x9c816e80…9d30

0x065c9d…c394

4 touches
1 conflict

0xaa854dcd…f2ce

0x065c9d…c394

3 touches
1 conflict

0xd9924653…42b8

0x065c9d…c394

3 touches
1 conflict

0x584241f7…5ad3

0x065c9d…c394

2 touches
0 conflicts

0x87c45405…7018

0x065c9d…c394

2 touches
0 conflicts

0x941ffa66…34e6

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity