pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,006,062
← previous block
next block →
recent activity
Analyzing
Block #92,006,062
8 transactions · 7 stateful · 2026-07-31 20:01:24 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,006,062
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x6a6cff8c
#6
setData
#7
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x225ef1d1…6dd4
0x34b655…2a6f
4 touches
1 conflict
0xd7e4217d…7c6b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x43e15ca4…039d
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0xebcd5c25…ae39
0x34b655…2a6f
2 touches
1 conflict
0x5ae70cdc…6411
0x34b655…2a6f
2 touches
1 conflict
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
0x225ef1d1bd…096dd4
Audit this contract →
← previous block
·
next block →
recent activity