pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,696,094
← previous block
next block →
recent activity
Analyzing
Block #96,696,094
11 transactions · 10 stateful · 2026-08-17 05:46:10 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,696,094
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
· blocks 2
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#2
matchOrders
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0xfe4e584c…50ff
0x754704…b603
4 touches
1 conflict
0x50be7f5d…2a30
0x754704…b603
4 touches
1 conflict
0xcbcfed5b…96a6
0x754704…b603
4 touches
1 conflict
0x0939bc15…c5e8
0x34b655…2a6f
2 touches
0 conflicts
0x44b80fe8…bfa7
0x34b655…2a6f
2 touches
0 conflicts
0x6bdb9869…7558
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b78
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:
0x103de0b5…25bb55
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity