pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,593,990
← previous block
next block →
recent activity
Analyzing
Block #95,593,990
9 transactions · 6 stateful · 2026-08-13 09:21:04 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,593,990
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
setData
#5
0x76cbb8…c00b
#6
0x59558d29
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c8d99a5…b937
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0c07ed0a…5cc4
0x34b655…2a6f
2 touches
0 conflicts
0x2f1de8d9…dbad
0x34b655…2a6f
2 touches
0 conflicts
0x37eae3e2…7724
0x34b655…2a6f
2 touches
0 conflicts
0x467347eb…350c
0x34b655…2a6f
2 touches
0 conflicts
0x4d3230f0…363a
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
0x3c8d99a5c5…07b937
Audit this contract →
← previous block
·
next block →
recent activity