Block #73,349,124

← previous blocknext block →recent activity

Analyzing

Block #73,349,124

35 transactions · 24 stateful · 2026-05-09 00:27:25 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,349,124  ·  35 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x22e295f5…1bef

0x065c9d…c394

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x83133451…e396

0xd32edf…ff58

7 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x0ef1e663…8f2a

0xaba216…a862

6 touches
3 conflicts

0x0175b7a6…1dba

0xaba216…a862

6 touches
3 conflicts

0x0175b7a6…1dbc

0xaba216…a862

6 touches
3 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

21 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity