← previous blocknext block →recent activity

Analyzing

Block #73,396,765

21 transactions · 15 stateful · 2026-05-09 05:44:21 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,396,765  ·  21 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x35129453…e354

0x065c9d…c394

4 touches
1 conflict

0x2abb1794…2439

0x065c9d…c394

3 touches
1 conflict

0xa25dc669…9aec

0x065c9d…c394

3 touches
1 conflict

0x550fd32e…8606

0x065c9d…c394

3 touches
1 conflict

0xd17e9f16…01cd

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

21 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity