pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,536,737
← previous block
next block →
recent activity
Analyzing
Block #97,536,737
11 transactions · 11 stateful · 2026-08-20 04:59:58 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,536,737
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
setData
#9
0x59558d29
#7
execFwdPositionOpsV2
#10
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765b5c31…586c
0x34b655…2a6f
4 touches
1 conflict
0x5d3bedbc…ba55
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0c7deec4…77cb
0x34b655…2a6f
2 touches
0 conflicts
0x1867b653…e61b
0x34b655…2a6f
2 touches
0 conflicts
0x5cfec795…7c0e
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
0x765b5c3188…52586c
Audit this contract →
← previous block
·
next block →
recent activity