pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,425,173
← previous block
next block →
recent activity
Analyzing
Block #102,425,173
39 transactions · 37 stateful · 2026-09-06 08:46:31 UTC
Parallelism
85
/100
Blocked
30
%
Avg conflicts / tx
0.46
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,425,173
· 39 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0xab083028
#4
0xab083028
· blocks 1
#6
0xab083028
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x5acec890
#10
0x5acec890
#11
0x5acec890
#12
0x5acec890
#13
0x5acec890
· blocks 1
#14
0x59558d29
· blocks 1
#16
setData
#17
artefact_keep
#18
execFwdPositionOpsV2
· blocks 4
#19
execFwdPositionOpsV2
#22
execFwdPositionOpsV2
#26
0x6a9d286a
· blocks 1
#28
execOrders
#29
execOrders
#30
execOrders
#31
execOrders
#32
execOrders
#33
execOrders
#36
execOrders
#37
execOrders
#38
execOrders
#5
0xab083028
#7
0xab083028
#15
0x59558d29
#20
execFwdPositionOpsV2
· blocks 3
#27
0x6a9d286b
#34
execOrders
· blocks 1
#21
execFwdPositionOpsV2
· blocks 2
#23
execFwdPositionOpsV2
· blocks 2
#24
execFwdPositionOpsV2
#25
execFwdPositionOpsV2
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
13
w0
14
w0
15
w1
18
w0
20
w1
21
w2
23
w3
24
w4
25
w4
26
w0
27
w1
34
w1
35
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x129d1b61…a1f0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x61fe66ad…cb68
0x34b655…2a6f
6 touches
3 conflicts
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
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
0x129d1b6132…ada1f0
Audit this contract →
← previous block
·
next block →
recent activity