pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,735,503
← previous block
next block →
recent activity
Analyzing
Block #97,735,503
9 transactions · 7 stateful · 2026-08-20 21:52:47 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
#97,735,503
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrder
#3
execOrder
· blocks 1
#4
updatePriceFeedsIfNecessary
#6
0x3f5c179b
#7
setData
#8
flashSwap
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x03f717cd…62de
0x34b655…2a6f
4 touches
1 conflict
0x0bc43347…93d4
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x6a3da303…403d
0x34b655…2a6f
4 touches
1 conflict
0x813e58b1…3a56
0x34b655…2a6f
4 touches
1 conflict
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
0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block
·
next block →
recent activity