pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,497,518
← previous block
next block →
recent activity
Analyzing
Block #90,497,518
12 transactions · 12 stateful · 2026-07-26 13:29:07 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,497,518
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
updatePrices
#3
execFwdPositionOps
· blocks 2
#5
forward
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a660c1a
#10
transfer
#11
setData
#4
execFwdPositionOps
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5931
0x34b655…2a6f
2 touches
0 conflicts
0x6561b826…f343
0x34b655…2a6f
2 touches
0 conflicts
0x69c497f8…e53a
0x34b655…2a6f
2 touches
0 conflicts
0x9efba1b3…4d54
0x34b655…2a6f
2 touches
0 conflicts
0xac8a5059…fd42
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity