pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,673,888
← previous block
next block →
recent activity
Analyzing
Block #86,673,888
36 transactions · 26 stateful · 2026-07-09 18:08:31 UTC
Parallelism
86
/100
Blocked
54
%
Avg conflicts / tx
0.64
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,673,888
· 36 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x6a4fe417
· blocks 1
#3
0xab083028
· blocks 1
#5
updatePrices
· blocks 3
#9
0x6a4fe417
#10
0x6a4fe417
#11
0x5a5d9a99
· blocks 1
#12
0x5a5d9a99
#13
0x5a5d9a99
#14
0x5a5d9a99
· blocks 1
#15
0x5a5d9a99
#17
updateDataFeedsValuesPartial
#19
execFwdPositionOps
#20
execFwdPositionOps
#21
executeBatch
· blocks 1
#24
0x0c7abd22
· blocks 1
#26
setData
#27
0x0563ba…f8f8
#28
0xc5788d…a7c5
#29
0x785f5745
#30
execOrders
· blocks 4
#34
execOrders
#2
0x6a4fe417
#4
0xab083028
· blocks 1
#6
updatePrices
· blocks 2
#16
0x5a5d9a99
#18
execFwdPositionOps
#22
executeBatch
#25
0xed82b078
#31
execOrders
· blocks 3
#7
updatePrices
· blocks 1
#23
0x3f5c179b
#32
execOrders
· blocks 2
#8
updatePrices
#33
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
w0
4
w1
5
w0
6
w1
7
w2
8
w3
11
w0
14
w0
16
w1
18
w1
21
w0
22
w1
23
w2
24
w0
25
w1
30
w0
31
w1
32
w2
33
w3
35
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity