← previous blocknext block →recent activity

Analyzing

Block #73,014,577

22 transactions · 16 stateful · 2026-05-07 11:21:33 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,014,577  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x73fc93b7…7afb

0x065c9d…c394

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0xeab16a30…8e2a

0x065c9d…c394

5 touches
3 conflicts

0xebcba71b…1fbc

0x065c9d…c394

5 touches
3 conflicts

0x0175b7a6…1db9

0x6ca43f…c331

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 0x0b390c6160…02dc07

← previous block·next block →recent activity