pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,449,309
← previous block
next block →
recent activity
Analyzing
Block #90,449,309
9 transactions · 8 stateful · 2026-07-26 09:26:34 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,449,309
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
setPriceForArbitrum
#3
setPrice
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8adcbf15…45e6
0x34b655…2a6f
4 touches
1 conflict
0x9f8a591e…d99b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd793c15e…7dba
0x34b655…2a6f
4 touches
1 conflict
0x007b42ba…13dc
0x34b655…2a6f
2 touches
0 conflicts
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x0aaef143…b27a
0x34b655…2a6f
2 touches
0 conflicts
0x2c390858…b1ed
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
0x8adcbf1591…ef45e6
Audit this contract →
← previous block
·
next block →
recent activity