pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,393,032
← previous block
next block →
recent activity
Analyzing
Block #92,393,032
10 transactions · 9 stateful · 2026-08-02 04:27:35 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,393,032
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
0x3f5c179b
#5
0x6a6ec7af
#6
setData
#7
execOrders
#8
updatePrices
#9
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0xb1e6a6a2…5d84
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2e
0x34b655…2a6f
4 touches
1 conflict
0x3818aa41…1372
0x34b655…2a6f
3 touches
1 conflict
0x34df840a…f19f
0x34b655…2a6f
2 touches
0 conflicts
0x3cda5e69…4037
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
0x4bf59d22eb…3300de
Audit this contract →
← previous block
·
next block →
recent activity