Block #73,353,174

← previous blocknext block →recent activity

Analyzing

Block #73,353,174

8 transactions · 6 stateful · 2026-05-09 00:54:26 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,353,174  ·  8 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0819ff02…0378

0x065c9d…c394

2 touches
0 conflicts

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x35a9e006…388d

0x065c9d…c394

2 touches
0 conflicts

0x5cb1ae64…9bd3

0x065c9d…c394

2 touches
0 conflicts

0x8cec3c6e…d138

0x065c9d…c394

2 touches
0 conflicts

0xa08e9962…8032

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