pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,724,896
← previous block
next block →
recent activity
Analyzing
Block #95,724,896
9 transactions · 7 stateful · 2026-08-13 20:20:34 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,724,896
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#5
transferWithAuthorization
#6
0x6a7e278a
#7
setData
#8
execOrders
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8146818…5583
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x0b710c61…e052
0x34b655…2a6f
2 touches
0 conflicts
0x151b88cc…996c
0x34b655…2a6f
2 touches
0 conflicts
0x18b16eda…c5b6
0x34b655…2a6f
2 touches
0 conflicts
0x1ab4c88c…49f2
0x34b655…2a6f
2 touches
0 conflicts
0x1ab4c88c…49f3
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
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
0xe81468189b…a15583
Audit this contract →
← previous block
·
next block →
recent activity