pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,013,470
← previous block
next block →
recent activity
Analyzing
Block #92,013,470
11 transactions · 10 stateful · 2026-07-31 20:38:39 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,013,470
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
execOrders
#8
transfer
#9
setData
#10
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb8f62bc…947e
0x34b655…2a6f
4 touches
1 conflict
0x39b8f346…e042
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7bd99c11…b714
0x34b655…2a6f
4 touches
1 conflict
0x9465bae8…d3ac
0x34b655…2a6f
4 touches
1 conflict
0x9c092d51…c906
0x34b655…2a6f
4 touches
1 conflict
0x9c092d51…c907
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
0xfb8f62bcfd…54947e
Audit this contract →
← previous block
·
next block →
recent activity