Block #73,469,053

← previous blocknext block →recent activity

Analyzing

Block #73,469,053

7 transactions · 6 stateful · 2026-05-09 13:45:28 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,469,053  ·  7 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

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0f20e35b…511d

0x34b655…2a6f

2 touches
0 conflicts

0x1d1799a9…c621

0x34b655…2a6f

2 touches
0 conflicts

0x37276d6c…ca84

0x34b655…2a6f

2 touches
0 conflicts

0x388f889f…a655

0x34b655…2a6f

2 touches
0 conflicts

0x3df2cf9c…ce34

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

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: 0x065c9d28…a9c394

3 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity