pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,018,278
← previous block
next block →
recent activity
Analyzing
Block #102,018,278
34 transactions · 30 stateful · 2026-09-04 22:24:33 UTC
Parallelism
65
/100
Blocked
50
%
Avg conflicts / tx
1.5
Longest chain
12
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,018,278
· 34 txs across 12 waves · depth 12
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
wave
w11
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6a9b4599
#4
0x6a9b4598
#6
0x5acec890
#8
0xab083028
#10
execOrder
#12
0x5acec890
#13
0x5acec890
#14
updateDataFeedsValuesPartial
#15
0x59558d29
#16
0x59558d29
#17
execPerpOps
#18
updateDataFeedsValuesPartial
#19
execPerpOps
#20
execPerpOps
#21
permit2TransferAndMulticall
#22
setData
#25
0xc7068c7b
#2
0x0c7abd22
· blocks 6
#5
0x5acec890
· blocks 6
#9
execOrders
· blocks 3
#7
execOrders
· blocks 2
#11
0x5acec890
· blocks 1
#23
execFwdPositionOpsV2
· blocks 4
#26
execOrders
· blocks 7
#24
execFwdPositionOpsV2
#27
execOrders
· blocks 6
#28
execOrders
· blocks 5
#29
execOrders
· blocks 4
#30
execOrders
· blocks 3
#31
execOrders
· blocks 2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
7
w3
9
w2
11
w3
23
w4
24
w5
26
w4
27
w5
28
w6
29
w7
30
w8
31
w9
33
w11
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity