pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,481,967
← previous block
next block →
recent activity
Analyzing
Block #90,481,967
11 transactions · 9 stateful · 2026-07-26 12:10:54 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,481,967
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
deposit
#3
aggregate3Value
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#9
0x6a65f9c6
#10
setData
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc2d4622…e7e9
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b828
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0xf961da8b…9367
0x34b655…2a6f
4 touches
1 conflict
0x2132931c…59f7
0x34b655…2a6f
4 touches
1 conflict
0x2132931c…59f8
0x34b655…2a6f
4 touches
1 conflict
0x31c5c046…a61a
0x34b655…2a6f
4 touches
1 conflict
0x3260c88b…0e32
0x34b655…2a6f
4 touches
1 conflict
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
0xbc2d462244…49e7e9
Audit this contract →
← previous block
·
next block →
recent activity