← previous blocknext block →recent activity

Analyzing

Block #73,273,912

31 transactions · 22 stateful · 2026-05-08 16:07:00 UTC

Parallelism

87/100

Blocked

45%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,273,912  ·  31 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x38f431b8…c65d

0x34b655…2a6f

6 touches
3 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

6 touches
3 conflicts

0x74877d13…d795

0xd32edf…ff58

5 touches
3 conflicts

0xba5743c7…21c3

0x1b6862…e19c

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity