pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,419,190
← previous block
next block →
recent activity
Analyzing
Block #98,419,190
11 transactions · 11 stateful · 2026-08-23 07:27:59 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,419,190
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0xab083028
· blocks 1
#4
execOrder
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#7
updatePriceFeedsIfNecessary
#8
execFwdPositionOpsV2
#9
execOrders
#10
setData
#3
0x8263f5d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x36249ab9…1570
0x34b655…2a6f
2 touches
0 conflicts
0x434c4769…7168
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5ecdeabd…940e
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: Settlement / Helper
1 conflict on slot
0xbb97db90cd…304c93
Audit this contract →
← previous block
·
next block →
recent activity