pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,513,003
← previous block
next block →
recent activity
Analyzing
Block #96,513,003
8 transactions · 6 stateful · 2026-08-16 14:25:18 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,513,003
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
updatePriceFeedsIfNecessary
#3
execFwdPositionOpsV2
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
4 touches
1 conflict
0xbf2c6707…4cbd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd106eb58…b2b2
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
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
0xe22ab637d9…007a8e
Audit this contract →
← previous block
·
next block →
recent activity