pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,770,485
← previous block
next block →
recent activity
Analyzing
Block #90,770,485
16 transactions · 15 stateful · 2026-07-27 12:22:15 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,770,485
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
setPrice
#3
setPrice
#4
setPrice
#5
setPrice
#6
setPrice
#7
setPrice
#8
setPrice
#9
updatePrices
#10
updateDataFeedsValuesPartial
#11
execFwdPositionOps
· blocks 1
#12
execOrders
#13
execFwdPositionOps
#15
setData
#14
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb46bb9bf…deb7
0x34b655…2a6f
4 touches
1 conflict
0x106c514d…bd94
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x10379e8d…3675
0x34b655…2a6f
2 touches
0 conflicts
0x170f3b5b…db60
0x34b655…2a6f
2 touches
0 conflicts
0x27378ed2…65bd
0x3c2269…cf62
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity