pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,203,583
← previous block
next block →
recent activity
Analyzing
Block #92,203,583
8 transactions · 8 stateful · 2026-08-01 12:34:49 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,203,583
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
setData
#7
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d09
0x34b655…2a6f
2 touches
0 conflicts
0x00958d6e…1d0a
0x34b655…2a6f
2 touches
0 conflicts
0x08442e85…5cb9
0x34b655…2a6f
2 touches
0 conflicts
0x278c4ae5…1639
0x34b655…2a6f
2 touches
0 conflicts
0x34b6e036…2161
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
0x9b2d3bee9d…d68eec
Audit this contract →
← previous block
·
next block →
recent activity