pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,793,179
← previous block
next block →
recent activity
Analyzing
Block #87,793,179
12 transactions · 11 stateful · 2026-07-14 22:52:37 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,793,179
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
execFwdPositionOps
· blocks 2
#9
forward
#10
0x6a56be2d
#11
setData
#7
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1912676…a60c
0x34b655…2a6f
4 touches
1 conflict
0x49ed4a1d…44a2
0x34b655…2a6f
4 touches
1 conflict
0xd3fde67c…9379
0x34b655…2a6f
4 touches
1 conflict
0xe2ce91e2…b99e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
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
0xb1912676b8…c5a60c
Audit this contract →
← previous block
·
next block →
recent activity