pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,770,911
← previous block
next block →
recent activity
Analyzing
Block #91,770,911
11 transactions · 10 stateful · 2026-07-31 00:18:26 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,770,911
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#4
updatePosition
#5
execOrders
#6
0x6a6bea4a
#7
execOrders
#8
setData
#10
0x59558d29
#3
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0xe5f9e3f4…2c61
0x34b655…2a6f
4 touches
1 conflict
0xe9a4c3e8…fc8c
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x2255b81f…ed13
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
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
0xdc8d7edd14…da8a03
Audit this contract →
← previous block
·
next block →
recent activity