pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,572,225
← previous block
next block →
recent activity
Analyzing
Block #98,572,225
12 transactions · 11 stateful · 2026-08-23 20:32:06 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,572,225
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#9
0x6a8b593e
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2f6ba854…a70d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x86dfd5…6a7d
2 touches
0 conflicts
0x00000000…0001
0x86dfd5…6a7d
2 touches
0 conflicts
0x00000000…0003
0x86dfd5…6a7d
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
0x38c6ff017b…61689f
Audit this contract →
← previous block
·
next block →
recent activity