pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,434,937
← previous block
next block →
recent activity
Analyzing
Block #96,434,937
11 transactions · 8 stateful · 2026-08-16 07:52:20 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,434,937
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
updatePriceFeedsIfNecessary
#6
0xd659cd30
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff4a358a…762f
0x34b655…2a6f
4 touches
1 conflict
0x791281d8…a6ea
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0xa1dbf4e4…9abd
0x34b655…2a6f
4 touches
1 conflict
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot
0xff4a358a00…50762f
Audit this contract →
← previous block
·
next block →
recent activity