pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,405,138
← previous block
next block →
recent activity
Analyzing
Block #92,405,138
8 transactions · 7 stateful · 2026-08-02 05:28:28 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,405,138
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x94defb17
#7
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff8fb7ba…30cc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x24a52b94…1d08
0x34b655…2a6f
4 touches
1 conflict
0x2b0418d5…0d92
0x34b655…2a6f
2 touches
0 conflicts
0x2f402f5d…7717
0x34b655…2a6f
2 touches
0 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
2 touches
0 conflicts
0x6b2ba712…0214
0x34b655…2a6f
2 touches
0 conflicts
0x9054fa69…8287
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
0xff8fb7ba4b…2c30cc
Audit this contract →
← previous block
·
next block →
recent activity