pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,480,651
← previous block
next block →
recent activity
Analyzing
Block #98,480,651
11 transactions · 10 stateful · 2026-08-23 12:37:34 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,480,651
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
0x59558d29
#4
updateDataFeedsValuesPartial
#5
0x5acec890
#6
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#10
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x644d1a8f…89bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03da5c00…b353
0x34b655…2a6f
2 touches
0 conflicts
0x05891ac8…ae45
0x34b655…2a6f
2 touches
0 conflicts
0x16ebf93b…ce00
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x3c7852ab…feea
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
0x5655f5c3b4…dd6b75
Audit this contract →
← previous block
·
next block →
recent activity