pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,436,465
← previous block
next block →
recent activity
Analyzing
Block #96,436,465
10 transactions · 8 stateful · 2026-08-16 08:00:01 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,436,465
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
batchRequestPriceCallback
#3
updateDataFeedsValuesPartial
#4
setData
#6
accrueYield
#7
handleOps
#8
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa01f2285…f16f
0x34b655…2a6f
4 touches
1 conflict
0x48719cbe…5484
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x9e6be63e…d886
0x34b655…2a6f
4 touches
1 conflict
0x14a727e7…cb57
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d8
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d9
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
0xa01f228537…b8f16f
Audit this contract →
← previous block
·
next block →
recent activity