pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,151,615
← previous block
next block →
recent activity
Analyzing
Block #95,151,615
6 transactions · 5 stateful · 2026-08-11 20:02:27 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,151,615
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
setData
#5
0x013f05…745f
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec0bdd60…3223
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7538
0x34b655…2a6f
2 touches
0 conflicts
0x0f97bf50…c21f
0x34b655…2a6f
2 touches
0 conflicts
0x3522af60…d679
0x34b655…2a6f
2 touches
0 conflicts
0x3b56f79b…310f
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:
Perpl
1 conflict on slot
0x2c2db8e9ef…f4fdc7
Audit this contract →
← previous block
·
next block →
recent activity