← previous blocknext block →recent activity

Analyzing

Block #73,482,524

13 transactions · 11 stateful · 2026-05-09 15:15:01 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,482,524  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x866bf367…7a60

0x188d58…ea8e

6 touches
3 conflicts

0x866bf367…7a61

0x188d58…ea8e

6 touches
3 conflicts

0x38aa1898…fdf5

0x1b6862…e19c

6 touches
3 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0x06db03a6…4692

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x25f8183e…b2d2

0x34b655…2a6f

2 touches
0 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: 0x188d586d…f9ea8e

3 conflicts on slot 0x866bf367c5…d57a60

← previous block·next block →recent activity