pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,683,593
← previous block
next block →
recent activity
Analyzing
Block #97,683,593
13 transactions · 13 stateful · 2026-08-20 17:29:39 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,683,593
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
updatePrices
#4
execOrder
· blocks 1
#5
execOrder
· blocks 1
#7
0x5acec890
#8
updateDataFeedsValuesPartial
#9
executeBatch
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
setData
#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
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xff8f5332…9827
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0d14b496…3dbc
0x34b655…2a6f
2 touches
0 conflicts
0x21861178…43aa
0x34b655…2a6f
2 touches
0 conflicts
0x2264a12f…dc16
0x34b655…2a6f
2 touches
0 conflicts
0x3861b165…8482
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
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity