pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,562,366
← previous block
next block →
recent activity
Analyzing
Block #97,562,366
9 transactions · 8 stateful · 2026-08-20 07:10:07 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,562,366
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#2
updatePrices
#5
execOrder
· blocks 1
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#3
updatePrices
· blocks 1
#6
execOrder
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x728f999a…832f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07bb71c0…3231
0x34b655…2a6f
2 touches
0 conflicts
0x0ae30f86…4f52
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x4c17a6f9…57bf
0x34b655…2a6f
2 touches
0 conflicts
0x7b3a71df…68d7
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:
0x103de0b5…25bb55
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity