pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,604,656
← previous block
next block →
recent activity
Analyzing
Block #96,604,656
11 transactions · 9 stateful · 2026-08-16 22:06:17 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,604,656
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
0x5acec890
· blocks 1
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
updatePriceFeedsIfNecessary
#10
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x02c7fac9…a15f
0x34b655…2a6f
2 touches
0 conflicts
0x071ce0dd…5606
0x34b655…2a6f
2 touches
0 conflicts
0x0b82a929…9a58
0x34b655…2a6f
2 touches
0 conflicts
0x1bc07c63…d6ad
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
0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block
·
next block →
recent activity