pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,595,044
← previous block
next block →
recent activity
Analyzing
Block #93,595,044
12 transactions · 11 stateful · 2026-08-06 09:15:21 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,595,044
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
updatePrices
#3
0x5acec890
· blocks 1
#4
0x3f5c179b
#5
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a745121
#10
setData
#11
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x595de029…7d05
0x34b655…2a6f
4 touches
1 conflict
0x947bb79d…6458
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x17091c69…e7f3
0x34b655…2a6f
2 touches
0 conflicts
0x18de67b0…bf35
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x1d9867ad…6d9a
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
0x595de0299f…ab7d05
Audit this contract →
← previous block
·
next block →
recent activity