pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,786,175
← previous block
next block →
recent activity
Analyzing
Block #90,786,175
14 transactions · 11 stateful · 2026-07-27 13:41:12 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,786,175
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a67606f
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
approve
#7
execFwdPositionOps
· blocks 1
#9
exactInputSingle
#10
batchUpdate
#11
execOrders
#12
setData
#13
0xc7e3ec2c
#3
updatePrices
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x356e3a8f…30de
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a05
0x34b655…2a6f
2 touches
0 conflicts
0x65104f89…bbce
0x34b655…2a6f
2 touches
0 conflicts
0x8a3e8c58…a6fe
0x34b655…2a6f
2 touches
0 conflicts
0x95a0333b…4779
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity