pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,419,810
← previous block
next block →
recent activity
Analyzing
Block #87,419,810
8 transactions · 8 stateful · 2026-07-13 05:14:41 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,419,810
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updatePriceFeedsIfNecessary
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a5474b9
#7
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0xb65883b1…0831
0x34b655…2a6f
4 touches
1 conflict
0xc105dd15…cbbc
0x34b655…2a6f
4 touches
1 conflict
0x13a157e0…215b
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
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
0x02991b41c5…1a19e6
Audit this contract →
← previous block
·
next block →
recent activity