pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,892,805
← previous block
next block →
recent activity
Analyzing
Block #90,892,805
10 transactions · 9 stateful · 2026-07-27 22:37:46 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,892,805
· 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
#6
0x57368ddf
#7
execOrders
#8
setData
#9
execOrders
#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
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x08803a9b…dfbd
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6a
0x34b655…2a6f
2 touches
0 conflicts
0x0a6e8942…fd6b
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a04
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
0xac8a5059ab…e9fd42
Audit this contract →
← previous block
·
next block →
recent activity