pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,014,105
← previous block
next block →
recent activity
Analyzing
Block #92,014,105
9 transactions · 7 stateful · 2026-07-31 20:41:51 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,014,105
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#6
0x6a6d0907
#7
setData
#8
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xae4a282a…f2ea
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec14f3f2…259a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x1a03a15f…8aef
0x447d2e…e9f5
2 touches
0 conflicts
0x3d02d821…2fcd
0x447d2e…e9f5
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
0x810a3aa264…c40227
Audit this contract →
← previous block
·
next block →
recent activity