pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,549,957
← previous block
next block →
recent activity
Analyzing
Block #92,549,957
9 transactions · 6 stateful · 2026-08-02 17:36:48 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,549,957
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
batchUpdate
#8
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0xa6862b62…d47f
0x34b655…2a6f
4 touches
1 conflict
0x0af22aa9…087c
0x34b655…2a6f
2 touches
0 conflicts
0x0af22aa9…087d
0x34b655…2a6f
2 touches
0 conflicts
0x0bf1341e…5fb1
0x34b655…2a6f
2 touches
0 conflicts
0x26dee23d…b18b
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0xbcab7dbe88…9e2825
Audit this contract →
← previous block
·
next block →
recent activity