Block #73,391,311

← previous blocknext block →recent activity

Analyzing

Block #73,391,311

8 transactions · 7 stateful · 2026-05-09 05:08:01 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,391,311  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6b1d8759…c965

0x065c9d…c394

4 touches
1 conflict

0xb2e2abf9…fd41

0x065c9d…c394

3 touches
1 conflict

0x2ac62f12…a7ca

0x065c9d…c394

3 touches
1 conflict

0xfcaa25b7…d24e

0x065c9d…c394

2 touches
0 conflicts

0xa7fe0d97…ae1c

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 0x4d87512b00…43897c

← previous block·next block →recent activity