pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,063,931
← previous block
next block →
recent activity
Analyzing
Block #100,063,931
35 transactions · 29 stateful · 2026-08-29 02:22:11 UTC
Parallelism
80
/100
Blocked
52
%
Avg conflicts / tx
0.94
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,063,931
· 35 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
execOrders
· blocks 5
#2
0x2f972d…5240
#3
0x6ad2e98b
#4
0xab083028
#5
0x8263f5d9
#6
execOrders
· blocks 1
#10
0x5acec890
#12
0x928e4afa
#13
updateDataFeedsValuesPartial
#16
0x59558d29
#17
0x59558d29
#18
execPerpOps
#19
execOrders
#20
setData
#21
setData
#28
batchUpdate
#30
0x57af42…c56c
#31
execOrders
· blocks 2
#32
execOrders
#7
execOrders
· blocks 2
#8
0x5acec890
· blocks 7
#9
0x5acec890
· blocks 2
#14
execOrder
· blocks 1
#15
execOrder
· blocks 3
#11
0x5acec890
· blocks 1
#22
execFwdPositionOpsV2
· blocks 2
#23
execFwdPositionOpsV2
· blocks 2
#25
execFwdPositionOpsV2
#24
execFwdPositionOpsV2
· blocks 2
#26
execFwdPositionOpsV2
· blocks 1
#33
execOrders
· blocks 1
#27
execFwdPositionOpsV2
· blocks 1
#34
execOrders
#29
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
7
w1
8
w1
9
w2
11
w3
14
w2
15
w2
22
w3
23
w3
24
w4
25
w3
26
w4
29
w6
33
w4
34
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98c943e…7c44
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
6 touches
3 conflicts
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
0xf98c943e1d…327c44
Audit this contract →
← previous block
·
next block →
recent activity