pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,015,273
← previous block
next block →
recent activity
Analyzing
Block #96,015,273
8 transactions · 8 stateful · 2026-08-14 20:41:31 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,015,273
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
· blocks 2
#4
execFwdPositionOpsV2
· blocks 1
#6
transfer
#7
setData
#3
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0xf073ab26…2c15
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xba0aa618…04aa
0x34b655…2a6f
3 touches
1 conflict
0xbd337aaf…cb5e
0x34b655…2a6f
2 touches
0 conflicts
0xc751242c…efac
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
0x31b3992285…921e65
Audit this contract →
← previous block
·
next block →
recent activity