pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,865,355
← previous block
next block →
recent activity
Analyzing
Block #92,865,355
11 transactions · 9 stateful · 2026-08-03 20:04:39 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,865,355
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcbbdb31a
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#8
0x6a70f4cf
#9
setData
#10
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x19b6e51f…0749
0x34b655…2a6f
2 touches
0 conflicts
0x19be00ce…7a97
0x34b655…2a6f
2 touches
0 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
2 touches
0 conflicts
0x1af1e5c8…36a0
0x34b655…2a6f
2 touches
0 conflicts
0x2d3930d3…c9b8
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
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity