pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,755,051
← previous block
next block →
recent activity
Analyzing
Block #92,755,051
10 transactions · 8 stateful · 2026-08-03 10:49:29 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,755,051
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x94defb17
#7
0x927825be
#8
setData
#9
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x096951fa…939d
0x34b655…2a6f
2 touches
0 conflicts
0x09890c88…213d
0x34b655…2a6f
2 touches
0 conflicts
0x0b419f60…8692
0x34b655…2a6f
2 touches
0 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
2 touches
0 conflicts
0x15516aa5…fc07
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity