pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,090,958
← previous block
next block →
recent activity
Analyzing
Block #98,090,958
33 transactions · 31 stateful · 2026-08-22 03:55:54 UTC
Parallelism
73
/100
Blocked
52
%
Avg conflicts / tx
1.21
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,090,958
· 33 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 5
#6
0x7b84f330
· blocks 1
#7
execOrders
· blocks 4
#8
execOrders
· blocks 1
#11
0x59558d29
#13
execOrder
· blocks 4
#14
updateDataFeedsValuesPartial
#15
execFwdPositionOpsV2
· blocks 1
#17
0x3f5c179b
#19
forward
#20
forward
#23
transferWithAuthorization
#24
transfer
#25
setData
#26
execOrders
#28
execOrders
#2
0x0c7abd22
· blocks 3
#9
execOrder
· blocks 4
#21
0xed82b078
· blocks 1
#32
0x7b84f330
#3
0x0c7abd22
· blocks 2
#10
execOrder
· blocks 2
#16
execFwdPositionOpsV2
· blocks 2
#22
0xed82b078
#4
0x0c7abd22
· blocks 1
#18
execFwdPositionOpsV2
· blocks 1
#5
0x0c7abd22
· blocks 1
#27
execOrders
· blocks 3
#12
0x5acec890
· blocks 1
#29
execOrders
· blocks 2
#30
execOrders
· blocks 1
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
6
w0
7
w0
8
w0
9
w1
10
w2
12
w5
16
w2
18
w3
21
w1
27
w4
29
w6
30
w7
32
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb33fab9f…f258
0xd32edf…ff58
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity