← previous blocknext block →recent activity

Analyzing

Block #73,223,749

35 transactions · 22 stateful · 2026-05-08 10:33:23 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,223,749  ·  35 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

0x8d7a97eb…d233

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065d

0x188d58…ea8e

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

0x29edc1ae…a06f

0x34b655…2a6f

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: 0xd32edf66…9fff58

10 conflicts on slot 0x8d7a97ebca…19d233

← previous block·next block →recent activity