pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,532,003
← previous block
next block →
recent activity
Analyzing
Block #97,532,003
12 transactions · 9 stateful · 2026-08-20 04:36:09 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,532,003
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
execFwdPositionOpsV2
#5
rebalanceFor
#6
setData
#7
0x59558d29
#8
execOrders
#9
execOrders
#10
execOrders
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x110e7ec7…cb90
0x000000…8ba3
2 touches
0 conflicts
0x1ff978e6…6e3f
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x5da19745…78ad
0x34b655…2a6f
2 touches
0 conflicts
0x66848050…644a
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:
0xc1570aa1…7ac91b
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity