pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,312,665
← previous block
next block →
recent activity
Analyzing
Block #92,312,665
9 transactions · 9 stateful · 2026-08-01 21:43:26 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,312,665
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#5
setData
#6
updatePrices
· blocks 1
#8
0x59558d29
#4
execFwdPositionOps
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3421c6d2…7f92
0x34b655…2a6f
2 touches
0 conflicts
0x4b1134d6…20c9
0x34b655…2a6f
2 touches
0 conflicts
0x508bbf1b…fe95
0x34b655…2a6f
2 touches
0 conflicts
0x5e716a03…4096
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:
0x91855e79…58ac7e
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity