← previous blocknext block →recent activity

Analyzing

Block #73,651,444

14 transactions · 12 stateful · 2026-05-10 10:00:52 UTC

Parallelism

57/100

Blocked

58%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,651,444  ·  14 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

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0x0175b7a6…1dbb

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbc

0x6c4bfa…a540

4 touches
1 conflict

0x0ef1e663…8f2a

0x6c4bfa…a540

4 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

6 conflicts on slot 0x7f81fb82c1…ec633e

← previous block·next block →recent activity