pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,322,584
← previous block
next block →
recent activity
Analyzing
Block #98,322,584
13 transactions · 13 stateful · 2026-08-22 23:21:59 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,322,584
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
#2
execOrders
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
0x928e4afa
· blocks 1
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
forward
#10
0x6a8a2f8f
#11
setData
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1731f0f…1f9d
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0x1d16804a…ead1
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x5b3a8d20…ccb1
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
0xa1731f0fa4…fc1f9d
Audit this contract →
← previous block
·
next block →
recent activity