pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,166,115
← previous block
next block →
recent activity
Analyzing
Block #87,166,115
10 transactions · 9 stateful · 2026-07-12 00:57:17 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,166,115
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#9
setData
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab98deda…aec4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0271422…696a
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x2e177343…2f8c
0x34b655…2a6f
4 touches
1 conflict
0x364ee443…4492
0x34b655…2a6f
4 touches
1 conflict
0x3be46a4b…26fb
0x34b655…2a6f
4 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
0xab98deda72…34aec4
Audit this contract →
← previous block
·
next block →
recent activity