pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,006,191
← previous block
next block →
recent activity
Analyzing
Block #92,006,191
11 transactions · 10 stateful · 2026-07-31 20:02:03 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,006,191
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
relay
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x59558d29
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0x821408cd…3dc7
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36b0
0x34b655…2a6f
4 touches
1 conflict
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x30197572…b682
0x34b655…2a6f
3 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
0x7e06d07b41…0636af
Audit this contract →
← previous block
·
next block →
recent activity