pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,545,686
← previous block
next block →
recent activity
Analyzing
Block #92,545,686
11 transactions · 11 stateful · 2026-08-02 17:15:20 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,545,686
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
execFwdPositionOps
· blocks 2
#4
handleOps
#7
updateTemporalNumericValuesV1
#8
setData
#9
execOrders
#10
0x59558d29
#5
execFwdPositionOps
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
2 touches
0 conflicts
0x64c887b9…0420
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity