pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,157,437
← previous block
next block →
recent activity
Analyzing
Block #88,157,437
9 transactions · 5 stateful · 2026-07-16 15:29:13 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,157,437
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrder
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
setData
#8
execOrders
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x13311674…9441
0x34b655…2a6f
2 touches
0 conflicts
0x13311674…9442
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x58bce2bb…a259
0x34b655…2a6f
2 touches
0 conflicts
0x59bfb0ed…ebd2
0x34b655…2a6f
2 touches
0 conflicts
0x5ba7204f…bdf1
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
0x9465204cd8…debf37
Audit this contract →
← previous block
·
next block →
recent activity