pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,386,782
← previous block
next block →
recent activity
Analyzing
Block #112,386,782
10 transactions · 9 stateful · 2026-10-11 05:36:37 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,386,782
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
· blocks 1
#5
executeBatch
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x0c7abd22
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94dabb65…43a3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x35542711…9be6
0x34b655…2a6f
2 touches
0 conflicts
0x35eab2e5…3c0a
0x34b655…2a6f
2 touches
0 conflicts
0x3afae44c…e494
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x84c6a4d9…0d4d
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
0x94dabb6529…f943a3
Audit this contract →
← previous block
·
next block →
recent activity