pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,688,944
← previous block
next block →
recent activity
Analyzing
Block #97,688,944
14 transactions · 13 stateful · 2026-08-20 17:56:44 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,688,944
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
#3
0x8263f5d9
#4
execOrder
· blocks 1
#5
execOrder
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
0x3f5c179b
#10
execFwdPositionOpsV2
#11
execOrders
#12
setData
#13
execOrders
#6
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x736c5b69…fb3f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x881e2535…0c7e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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
0xec7d120df9…5d7084
Audit this contract →
← previous block
·
next block →
recent activity