pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,870,633
← previous block
next block →
recent activity
Analyzing
Block #92,870,633
11 transactions · 11 stateful · 2026-08-03 20:31:12 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,870,633
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
handleOps
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
execOrders
#7
0x6a70fb07
#8
setData
#9
execOrders
#10
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x58123a85…6f7d
0x34b655…2a6f
4 touches
1 conflict
0x33a26eb2…2df0
0x5ff137…2789
2 touches
0 conflicts
0xaf831072…51d5
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51d6
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51d7
0x69a5f9…2fef
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
0x628359b1c9…1a7263
Audit this contract →
← previous block
·
next block →
recent activity