pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,115,867
← previous block
next block →
recent activity
Analyzing
Block #90,115,867
10 transactions · 10 stateful · 2026-07-25 05:12:54 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,115,867
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
multicall
#7
0x3f5c179b
#8
setData
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab5ba139…ea6f
0x34b655…2a6f
4 touches
1 conflict
0x4f0b1eca…aead
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x75b76018…4932
0x34b655…2a6f
2 touches
0 conflicts
0x762f8713…a47d
0x34b655…2a6f
2 touches
0 conflicts
0x76d36e11…fde2
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
0xab5ba139f3…9fea6f
Audit this contract →
← previous block
·
next block →
recent activity