pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,419,992
← previous block
next block →
recent activity
Analyzing
Block #92,419,992
11 transactions · 9 stateful · 2026-08-02 06:43:09 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,419,992
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#6
execOrders
#7
0x6a6ee775
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#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
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b7094d9…4373
0x34b655…2a6f
2 touches
0 conflicts
0x154f65cf…14d6
0x34b655…2a6f
2 touches
0 conflicts
0x16619921…0b9d
0x34b655…2a6f
2 touches
0 conflicts
0x19fb7d60…da48
0x34b655…2a6f
2 touches
0 conflicts
0x1c796c6b…064e
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
0x4efae87285…886aa8
Audit this contract →
← previous block
·
next block →
recent activity