Block #73,501,584

← previous blocknext block →recent activity

Analyzing

Block #73,501,584

11 transactions · 7 stateful · 2026-05-09 17:21:56 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,501,584  ·  11 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

0xf4191528…cfff

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x10f4de05…8478

0x065c9d…c394

2 touches
0 conflicts

0xd1e14d06…9f08

0x065c9d…c394

2 touches
0 conflicts

0xf1085f44…f1a7

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0x0175b7a6…1db9

0x6c4bfa…a540

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