pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,527,177
← previous block
next block →
recent activity
Analyzing
Block #102,527,177
33 transactions · 30 stateful · 2026-09-06 17:23:39 UTC
Parallelism
70
/100
Blocked
50
%
Avg conflicts / tx
1.09
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,527,177
· 33 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
· blocks 4
#3
updatePrices
#5
0xab083028
· blocks 2
#7
0xab083028
#8
execOrder
· blocks 2
#10
updateDataFeedsValuesPartial
#12
0x5acec890
#15
0x4cb2db39
#16
0x59558d29
#17
approve
#18
mergePositions
#19
setData
#24
updateTemporalNumericValuesV1
#26
0xed82b078
#30
execOrders
#32
execOrders
#4
0x5acec890
· blocks 4
#6
0xab083028
· blocks 1
#9
execOrder
· blocks 2
#27
0xed82b078
#11
0x5acec890
· blocks 5
#25
0xed82b078
#13
0x5acec890
· blocks 2
#20
execFwdPositionOpsV2
· blocks 4
#14
0x5acec890
· blocks 1
#21
execFwdPositionOpsV2
· blocks 3
#22
execFwdPositionOpsV2
· blocks 2
#23
execFwdPositionOpsV2
· blocks 1
#28
execOrders
· blocks 2
#29
execOrders
· blocks 1
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
8
w0
9
w1
11
w2
13
w3
14
w4
20
w3
21
w4
22
w5
23
w6
25
w2
27
w1
28
w7
29
w8
31
w9
- 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
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x256918f1…c4d0
0x34b655…2a6f
8 touches
6 conflicts
0xbd22d0fc…64fd
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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