pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,697,280
← previous block
next block →
recent activity
Analyzing
Block #92,697,280
11 transactions · 9 stateful · 2026-08-03 05:58:42 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
#92,697,280
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 2
#5
executeBatch
#7
0x6ac064…e0fd
#8
0x68b76c…fbb3
#9
setData
#10
0xc7e3ec2c
#4
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf133863f…c6fb
0x34b655…2a6f
4 touches
1 conflict
0xe2f7aa42…ae50
0x34b655…2a6f
4 touches
1 conflict
0x3689ccb9…566f
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x62af5969…79fb
0x34b655…2a6f
4 touches
1 conflict
0x62af5969…79fc
0x34b655…2a6f
4 touches
1 conflict
0x7157c635…856c
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity