Block #73,384,034

← previous blocknext block →recent activity

Analyzing

Block #73,384,034

20 transactions · 15 stateful · 2026-05-09 04:19:36 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,384,034  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x11014466…f718

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x621ee95a…fbbf

0x065c9d…c394

3 touches
1 conflict

0x0d58ee92…a6b6

0x065c9d…c394

3 touches
1 conflict

0x2dbaa2ec…a19c

0x065c9d…c394

3 touches
1 conflict

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity