Block #73,500,036

← previous blocknext block →recent activity

Analyzing

Block #73,500,036

9 transactions · 7 stateful · 2026-05-09 17:11:37 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,500,036  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x03833adf…b96f

0x065c9d…c394

2 touches
0 conflicts

0x19167fc5…a9a6

0x065c9d…c394

2 touches
0 conflicts

0x3016a6a7…c636

0x065c9d…c394

2 touches
0 conflicts

0x551de9fa…a736

0x065c9d…c394

2 touches
0 conflicts

0x6e78b2b7…c353

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

1 conflict on slot 0x4d87512b00…43897c

← previous block·next block →recent activity