pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,455,876
← previous block
next block →
recent activity
Analyzing
Block #93,455,876
10 transactions · 10 stateful · 2026-08-05 21:35:46 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,455,876
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execPerpOps
#3
0xeb282f7f
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
0x57368ddf
#8
setData
#9
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x74422cde…e5aa
0x1efe02…37d6
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x1ea2c53b…887a
0x754704…b603
2 touches
0 conflicts
0x2edbccf6…cc14
0x754704…b603
2 touches
0 conflicts
0x3d19ddf7…ac25
0x754704…b603
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
0x4e8c4408ae…50d37a
Audit this contract →
← previous block
·
next block →
recent activity