pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,579,980
← previous block
next block →
recent activity
Analyzing
Block #92,579,980
10 transactions · 9 stateful · 2026-08-02 20:07:48 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,579,980
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#7
0x6a6fa40c
#8
setData
#9
0x59558d29
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5f815e7…c83e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1efc452b…354f
0x34b655…2a6f
4 touches
1 conflict
0x1efc452b…3550
0x34b655…2a6f
4 touches
1 conflict
0x2dc33e18…3b26
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf009b1a8…d02d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
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
0xf5f815e72d…45c83e
Audit this contract →
← previous block
·
next block →
recent activity