← previous blocknext block →recent activity

Analyzing

Block #73,596,490

18 transactions · 16 stateful · 2026-05-10 03:52:38 UTC

Parallelism

72/100

Blocked

69%

Avg conflicts / tx

1.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,596,490  ·  18 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

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0x87e28d96…2a45

0x34b655…2a6f

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

10 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity