pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,722,518
← previous block
next block →
recent activity
Analyzing
Block #90,722,518
11 transactions · 9 stateful · 2026-07-27 08:20:59 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,722,518
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 2
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#7
execFwdPositionOps
#8
execOrders
#9
setData
#10
exactInputSingle
#3
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1e1bee47…1efa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x6128fbe6…e285
0x34b655…2a6f
2 touches
0 conflicts
0x77e6f43a…0dee
0x34b655…2a6f
2 touches
0 conflicts
0x8ebba059…7439
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
0x3bdd71a21a…eeb6eb
Audit this contract →
← previous block
·
next block →
recent activity