← previous blocknext block →recent activity
Analyzing
Block #73,752,046
15 transactions · 15 stateful · 2026-05-10 21:19:45 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,752,046 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w18w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2657f5…e008
0x34b655…2a6f
8 touches
6 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0x0c52cabc…caba
0x34b655…2a6f
6 touches
3 conflicts
0xd53220ed…4739
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2eab2661…2b15
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: Perpl
6 conflicts on slot 0x8a2657f5c3…4ce008
Audit this contract →
← previous block·next block →recent activity