pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,689,144
← previous block
next block →
recent activity
Analyzing
Block #92,689,144
10 transactions · 10 stateful · 2026-08-03 05:17:44 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,689,144
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
execFwdPositionOps
#4
updatePosition
#6
setData
#7
modifyLiquidities
#8
modifyLiquidities
#9
0x59558d29
#2
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x19439a65…eb51
0x34b655…2a6f
4 touches
1 conflict
0x3270d9f8…099a
0x34b655…2a6f
2 touches
0 conflicts
0x4a946f2d…0be0
0x34b655…2a6f
2 touches
0 conflicts
0x4e8c4408…d37a
0x34b655…2a6f
2 touches
0 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
2 touches
0 conflicts
0x698d5e17…b316
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity