← previous blocknext block →recent activity
Analyzing
Block #95,268,932
18 transactions · 15 stateful · 2026-08-12 06:01:17 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,268,932 · 18 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
1w02w13w24w15w06w07w18w29w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x659e6618…dfa7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1526b11f…8b21
0x34b655…2a6f
6 touches
3 conflicts
0xb56f0740…7542
0x34b655…2a6f
6 touches
3 conflicts
0x0bd48698…296c
0xd32edf…ff58
5 touches
3 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
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 0x659e6618aa…39dfa7
Audit this contract →
← previous block·next block →recent activity