pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,647,270
← previous block
next block →
recent activity
Analyzing
Block #98,647,270
12 transactions · 10 stateful · 2026-08-24 03:02:41 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,647,270
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x928e4afa
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
0x3f5c179b
#7
execFwdPositionOpsV2
#8
transfer
#9
setData
#10
execOrders
#2
0x928e4afa
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf37f77e…a027
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1d26d55a…aacd
0x34b655…2a6f
2 touches
0 conflicts
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x3ebcba29…6dca
0x34b655…2a6f
2 touches
0 conflicts
0x41976311…1080
0x34b655…2a6f
2 touches
0 conflicts
0x5784baac…ac7e
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
0xcf37f77e49…18a027
Audit this contract →
← previous block
·
next block →
recent activity