pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,501,469
← previous block
next block →
recent activity
Analyzing
Block #98,501,469
35 transactions · 33 stateful · 2026-08-23 14:22:50 UTC
Parallelism
80
/100
Blocked
45
%
Avg conflicts / tx
0.86
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,501,469
· 35 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#3
matchOrders
#5
0xab083028
· blocks 2
#6
0x6ad2e98b
#7
0xab083028
· blocks 2
#11
execOrder
· blocks 4
#12
updateDataFeedsValuesPartial
#13
0x59558d29
#14
execPerpOps
· blocks 1
#15
transferAndMulticall
#17
execOrder
#21
0x3f5c179b
#22
executeBatch
#24
0x3f5c179b
· blocks 1
#25
0x3f5c179b
#27
forward
#30
0x6a8b02b2
#31
setData
#32
0xb06fdc…3fba
#2
0x0c7abd22
· blocks 3
#4
execOrders
· blocks 2
#8
0x8263f5d9
#16
execPerpOps
#23
0x3f5c179b
#28
0xed82b078
· blocks 1
#9
execOrders
· blocks 1
#18
execFwdPositionOpsV2
· blocks 4
#29
0xed82b078
#10
execOrders
#19
execFwdPositionOpsV2
· blocks 2
#20
execFwdPositionOpsV2
· blocks 1
#26
execFwdPositionOpsV2
· blocks 1
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
5
w0
7
w0
8
w1
9
w2
10
w3
11
w0
14
w0
16
w1
18
w2
19
w3
20
w3
23
w1
26
w4
28
w1
29
w2
33
w5
34
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xea7bceb0…a370
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x1d48c0e2…b62e
0x34b655…2a6f
6 touches
3 conflicts
0x2bfc672f…4d28
0x34b655…2a6f
6 touches
3 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
6 touches
3 conflicts
0x71fad9ce…c11f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity