pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,287,293
← previous block
next block →
recent activity
Analyzing
Block #102,287,293
36 transactions · 33 stateful · 2026-09-05 21:08:05 UTC
Parallelism
83
/100
Blocked
45
%
Avg conflicts / tx
0.67
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,287,293
· 36 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#4
0x6df9e92b
#5
updatePrices
#6
0xab083028
#9
execOrders
· blocks 1
#11
0x5acec890
#12
0x5acec890
#13
0x5acec890
· blocks 3
#16
0x5acec890
#17
execOrder
· blocks 1
#18
0x59558d29
· blocks 1
#20
execPerpOps
#21
execPerpOps
#22
0x6a9c84b8
#23
updateDataFeedsValuesPartial
#24
setData
· blocks 1
#25
setData
#28
execFwdPositionOpsV2
· blocks 2
#29
execFwdPositionOpsV2
#32
0x6a9c84b8
#2
0x0c7abd22
· blocks 2
#10
execOrders
#14
0x5acec890
· blocks 3
#19
0x59558d29
#26
setData
#27
execFwdPositionOpsV2
· blocks 1
#30
execFwdPositionOpsV2
#3
0x0c7abd22
· blocks 1
#7
0xab083028
#15
0x5acec890
· blocks 1
#31
execFwdPositionOpsV2
#8
0xab083028
#33
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w2
8
w3
9
w0
10
w1
13
w0
14
w1
15
w2
17
w0
18
w0
19
w1
24
w0
26
w1
27
w1
28
w0
30
w1
31
w2
33
w3
34
w4
35
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb82f494f…db33
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b478
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot
0xb82f494f98…19db33
Audit this contract →
← previous block
·
next block →
recent activity